Backend discovery
ArchPilot identifies twenty-server as the governed backend instead of treating the repository only as frontend and library packages.
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 relationships, 2 errors.
ArchPilot recognized Twenty as a mixed NestJS, React, and shared-library monorepo, identified twenty-server as the backend, connected GraphQL and PostgreSQL resources to that backend, and produced 17 governed components with 16 architecture relationships.
The run shows backend discovery in a large TypeScript monorepo, keeps test-only and scaffold-template packages outside default governed components, and separates two deterministic boundary findings in documentation tooling from warnings that require 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.
Resource mapping
GraphQL and PostgreSQL resources are connected to the backend in the architecture model.
Governed scope
Test-only, lint-tooling, and scaffold-template packages stay outside the default governed component set.
Review triage
The result distinguishes deterministic boundary evidence from warning categories that need human interpretation.
Findings
What deserves attention
346 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.
Confirmed dependency-boundary evidence
The docs navigation file imports internal constants from twenty-shared instead of its public entrypoint.
Database/query review signals
Backend query and persistence patterns produce review evidence for bounded reads, direct persistence usage, and query-risk volume.
Application/domain responsibility review signals
Large services, broad domain boundaries, and direct database access deserve human architecture review.
Scope/context notes
ADR expectations and dependency-hub evidence provide governance context rather than production-runtime defect claims.
Confirmed architecture evidence
Docs navigation bypasses a shared public entrypoint
Both AP-DEP-003 errors occur in packages/twenty-docs/navigation/supported-languages.ts, where documentation tooling imports internal paths from twenty-shared/src/constants instead of the shared package public entrypoint.
Review signal
Backend database access creates review volume
Backend services and command handlers include database and persistence access patterns that ArchPilot groups as query and direct-persistence review evidence, not automatic production defects.
Application and domain boundaries deserve focused review
Large services and broad domain-responsibility signals help reviewers choose where to inspect ownership boundaries first.
Scope-dependent observation
The two errors are documentation/tooling scope
The imports bypass the shared package's declared public entrypoint, but their operational impact is limited to documentation tooling rather than the production server.
How to interpret this validation
- Both errors are confined to documentation tooling. They identify imports that bypass the generated public package boundary. This may be an accepted repository convention, but intent was not established by this independent analysis, and the production server is not affected.
- Warnings are architecture review signals. Heuristic warnings require human interpretation.
- 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.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
- twentyhq/twenty
- Branch
- main
- Commit date
- 2026-08-20T07:55:51+00: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
AB273661931CFA35FFC5BA42EFD3D42290318E52B7159082BDACD887F54045E2
Artifact hashes
- architecture.json
AB273661931CFA35FFC5BA42EFD3D42290318E52B7159082BDACD887F54045E2- validation-status.json
42E23C30AD10C78B826089473A42283A7E95923AED29BED12DF626577C5A8BF9- architecture-map.json
4C5BBAD1EAAEC063D59BBB3E1FB736725DB4F080E747BB313820F966F4C86557- architecture-review-report.json
2094A2727468CCC97556C21C0D5CD976AE407617E486A69C19C3849027755F41
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.