Evidence
We validate substantial open-source repositories so you can see the architecture ArchPilot discovers, the findings it raises, and the judgment needed to interpret them well.
TypeScript, NestJS, React, GraphQL, PostgreSQL
A TypeScript CRM monorepo with a NestJS backend, React frontend packages, shared libraries, GraphQL, and PostgreSQL.
The run shows that ArchPilot can model a large mixed monorepo while making analysis scope and warning volume visible for human review.
View validationTypeScript, NestJS, Angular, React, GraphQL
A TypeScript commerce platform with NestJS backend packages, frontend packages, plugins, and shared libraries.
The run shows a strong 0.2.10 TypeScript monorepo result: complete dependency evidence, clear backend/frontend/library structure, and reviewable warnings without error-level findings.
View validationJava, Spring, Maven reactor
A Java and Spring multi-module repository with core libraries, event integrations, observability modules, examples, and integration tests.
The run shows nested module discovery, dependency hubs in shared event infrastructure, and scope-dependent event findings where examples and integration-test modules are intentionally governed.
View validationTypeScript, NestJS, Nx monorepo
A NestJS and TypeScript monorepo with generated-service, platform, server, and supporting package structure.
The run gives reviewers a governed structure, dependency evidence, and review priorities while keeping partial dependency coverage visible.
View validationJava, Spring, Maven reactor
A large Java and Spring workflow engine repository with engine, REST, integration, and supporting modules.
The run is a strong large-scale Java dependency-map example with established dependency analysis and a visible API-detection caveat.
View validationMethod
We record the repository URL, branch, commit SHA, and commit date before running ArchPilot.
We run each validation with a published ArchPilot CLI release and record the exact version with the repository evidence.
We show exact metrics only when the warnings and scope can be explained without implying endorsement.
How to read scores
Architecture Health reflects findings against the generated model. Setup Readiness reflects whether the repository has enough configuration and artifacts for governance. Warnings often require human review.
