Architecture inventory
The repository becomes a 12-component model instead of a pile of package folders.
Repository validation
Vendure
A TypeScript commerce platform with NestJS backend packages, frontend packages, plugins, and shared libraries.
Independent analysis of a public repository. This project is not affiliated with or endorsed by ArchPilot. Product and project names are used only for identification.
See something inaccurate? Contact us.What ArchPilot found
12 components, 8 relationships, no errors.
ArchPilot modeled Vendure as a 12-component TypeScript monorepo spanning NestJS backend packages, Angular and React frontend packages, plugins, and shared libraries.
The run shows how ArchPilot turns a large commerce monorepo into a readable architecture inventory, highlights the core package as a dependency hub, and separates error-free validation from warnings that deserve review.
Source-backed architecture units
Mapped module dependencies
Blocking validation findings
Items for review, not confirmed defects
Why it is useful
From repository shape to reviewable architecture signals.
The point is not to score open-source projects against each other. The point is to show how local validation turns repository structure into a model teams can inspect and govern.
Dependency hubs
Core package coupling is visible through declared and actual dependency evidence.
Review focus
Warnings point reviewers toward large services, collection reads, and transaction-sensitive paths.
Governance baseline
Generated contracts give teams a starting point for local validation and CI policy.
Findings
What deserves attention
68 normalized finding clusters
Findings below are grouped into areas so readers can see what is deterministic architecture evidence, what is a review signal, and what depends on governance scope.
Dependency hub
packages-core has eight declared and actual inbound dependencies.
Collection reads
Several ORM reads return collections without visible pagination evidence.
Application services
Large services with many methods or collaborators are flagged for review.
Ownership boundaries
Some services are large enough to suggest broad ownership boundaries.
Repository responsibilities
Repository or service methods contain behavior worth human review.
Transaction boundaries
Transaction-sensitive code paths were identified for review.
Decision context
The generated governance model expects ADR context for API style and dependency governance.
Confirmed architecture evidence
Core package is an architectural hub
The dependency map reports packages-core with eight declared and actual inbound dependencies.
Review signal
Order service carries broad application responsibility
OrderService has many collaborators and methods, so ArchPilot presents it as an oversized-service signal rather than an error.
Shipping-method cleanup reads active orders as a collection
removeShippingMethodFromActiveOrders uses getMany on active orders constrained by channel and shipping method. The constraint matters, so this is published as a review signal with context.
How to interpret this validation
- Generated configuration affects governance scope and should be reviewed before adoption.
- Warnings are not confirmed project defects. Many are heuristic review signals.
- Scores describe conformance to the generated model and supported rules, not a ranking against other projects.
- This is independent analysis of a public repository, not maintainer endorsement.
Reproduce and verify
Run from commit 9018f1780d65 with ArchPilot 0.2.5.
Exact CLI commands
npx --yes @archpilotlabs/[email protected] init --yes
npx --yes @archpilotlabs/[email protected] validate --json
npx --yes @archpilotlabs/[email protected] map --json
npx --yes @archpilotlabs/[email protected] report --jsonRepository provenance
- Repository
- vendurehq/vendure
- Branch
- master
- Commit date
- 2026-08-14T11:02:36+02:00
- Validation date
- Aug 21, 2026
Package and configuration proof
- Package
@archpilotlabs/archpilot@0.2.5- Tarball
- npm package tarball
- Integrity
sha512-EMyKdhnEREogSSqjfWzQzUzSzftERVqyUtSfpoEQEe3TaQfo2qG1AFvo5pwxmz4RgJ8yLqy5j4MX1fD13Nnzwg==- Config hash
9B868FFD5203BC40FDDFC58E2D17BA7AC37F1E5FC13E294B3B90262F7664BBD8
Artifact hashes
- architecture.json
9B868FFD5203BC40FDDFC58E2D17BA7AC37F1E5FC13E294B3B90262F7664BBD8- validation-status.json
0C54FC803A2752F74A74F1BC78D07FC566D6115FA2953D3460778B4660166D73- architecture-map.json
55815CA3DDC303F02167AEAEC467D679004638EB941A822035835BEE719BFF4D- architecture-review-report.json
196952E36EB3D940E90E62C81708D3FCA065213C3A92DE13D05096E2935633DB
Try it locally
Run the same workflow on your repository.
The extension and CLI validate architecture locally. ArchPilot Cloud brings those results together for shared history, policy workflows, cross-repository intelligence, and organization-wide governance.