Monorepo modeling
ArchPilot maps a large mixed NestJS, React, GraphQL, and shared-library repository into 17 reviewable architecture components.
Repository validation
Twenty
A TypeScript CRM monorepo with a NestJS backend, React frontend packages, shared libraries, GraphQL, and PostgreSQL.
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
17 components, 16 mapped relationships.
ArchPilot modeled Twenty as a large NestJS, React, GraphQL, and shared-library monorepo with 17 architecture components and 16 mapped relationships.
The run shows that ArchPilot can model a large mixed monorepo while making analysis scope and warning volume visible for human review.
Source-backed architecture units
Mapped module dependencies
Blocking validation findings
Items for review, not confirmed defects
Dependency analysis covered 13,972 TypeScript sources, but two supported sources could not be fully analyzed.
- Analyzed sources
- 13972
- Unsupported sources
- 2
Affected dependency conclusions are presented conservatively rather than as definitive clean or violation results.
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.
Relationship mapping
The architecture graph preserves 16 mapped relationships for reviewers to inspect.
Scope visibility
Partial dependency evidence makes confidence limits visible on the public page.
Review triage
Warnings and DQR findings are framed as review signals requiring human interpretation.
Findings
What deserves attention
451 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 boundary evidence
Two error-level AP-DEP-003 findings occur in documentation navigation, with one partial-analysis guidance row for the same rule.
Dependency capability guidance
Partial dependency analysis produced informational guidance for affected dependency conclusions.
Dependency hubs
Three modules have high inbound dependency counts in the architecture map.
Database/query review signals
DQR volume includes migration and upgrade-related code, so it should be reviewed cautiously rather than treated as a defect count.
Application and governance review signals
Large mixed-monorepo warning volume helps prioritize human architecture review.
Review signal
Backend database access creates review volume
DQR volume includes migration and upgrade-related code, so ArchPilot presents this as review evidence rather than a claim that each warning is a production defect.
Application and domain boundaries deserve focused review
Large services, ownership boundaries, and governance signals help reviewers choose where to inspect first in a large repository.
Scope-dependent observation
Dependency findings are scope-sensitive
The preserved 0.2.10 report shows two error-level AP-DEP-003 findings in packages/twenty-docs/navigation/supported-languages.ts, a documentation navigation file.
How to interpret this validation
- The preserved 0.2.10 report shows the two error-level AP-DEP-003 findings in documentation navigation scope.
- DQR volume includes migration and upgrade-related code and should be interpreted cautiously.
- Dependency analysis was partial, so affected conclusions are surfaced conservatively.
- Scores are context for this generated model and supported rules, not repository rankings.
- This validation is independent and does not imply Twenty endorsement, approval, partnership, or maintainer involvement.
Reproduce and verify
Run from commit 3cf714fc270e with ArchPilot 0.2.10.
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
- twentyhq/twenty
- Branch
- main
- Commit date
- 2026-08-20T12:54:39Z
- Validation date
- Sep 10, 2026
Package and configuration proof
- Package
@archpilotlabs/archpilot@0.2.10- Tarball
- npm package tarball
- Integrity
sha512-2V0WfNnvZVS/ey7ndKkhvYBI2YqIkrNTwkFmpMdjkMrb2RQuN7uDYCsOW2dVDPOqyf2q86V3gnc38i2jENGQOg==- Config hash
816F7A083434D06EACC183BF7C45F36BE90E1426CDC69DE2ABD140D68210B340
Artifact hashes
- architecture.json
816F7A083434D06EACC183BF7C45F36BE90E1426CDC69DE2ABD140D68210B340- validation-status.json
10DAE8833EA7FF6C21200046BAB0BB15B6EB40DC407E52D844D8A075E30F4200- architecture-map.json
E560113D3260D62D01F93731FB377E62F18C86D90564D71D0F24189EE0FE3028- architecture-review-report.json
7C69E224CA85E93EEF9E943539499F0E9A00769F5A039774E4786FF948F5ECE7
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.