Repository validation

Amplication

A NestJS and TypeScript monorepo with generated-service, platform, server, and supporting package structure.

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

24 architecture nodes, 7 mapped relationships.

ArchPilot modeled Amplication as a NestJS and TypeScript monorepo with 24 architecture nodes and 7 mapped relationships.

The run gives reviewers a governed structure, dependency evidence, and review priorities while keeping partial dependency coverage visible.

Components
24

Source-backed architecture units

Relationships
7

Mapped module dependencies

Errors
0

Blocking validation findings

Warnings
190

Items for review, not confirmed defects

Dependency analysis
Partial

Dependency analysis covered 867 TypeScript sources, but one supported source could not be fully analyzed.

Analyzed sources
867
Unsupported sources
1

Affected dependency conclusions are surfaced conservatively rather than presented 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.

Architecture discovery

ArchPilot maps 24 architecture nodes in a substantial TypeScript/NestJS repository.

Governed structure

The generated model gives reviewers a compact starting point for module and dependency review.

Partial capability caveat

Dependency coverage limits are visible instead of hidden behind a clean result.

Review prioritization

Warnings help focus query and application-structure review without overstating defects.

Findings

What deserves attention

141 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.

Partial dependency evidence

Partial dependency coverage is visible, so dependency conclusions need scope-aware review.

Count
10
Interpretation
Scope-dependent observation
Rule
AP-DEP-001/AP-DEP-002/AP-DEP-003/AP-DEP-004/AP-DEP-005/AP-DEP-006/AP-DEP-007/AP-DEP-008/AP-DEP-009/AP-DEP-010

Database/query review signals

Query-risk warnings are review prompts rather than confirmed defects.

Count
82
Interpretation
Review signal
Rule
AP-DQR-003/AP-DQR-005/AP-DQR-006/AP-DQR-007

Architecture review signals

The run surfaces structure and review priority across a large NestJS monorepo.

Count
108
Interpretation
Review signal
Rule
AP-APP-003/AP-APP-005/AP-DOM-003/AP-EVT-001/AP-ADR-004

Review signal

Scope-dependent observation

Dependency coverage is partial

The public result presents Amplication as credible but caveated because dependency evidence was partial.

Source
Architecture review report

How to interpret this validation

  • Dependency analysis was partial, so affected conclusions are surfaced conservatively.
  • Query-risk warnings should not be overstated as confirmed defects.
  • 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 7656495d27f0 with ArchPilot 0.2.10.

View commit
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 --json
Repository provenance
Branch
master
Commit date
2026-04-02T16:51:06Z
Validation date
Sep 10, 2026
Package and configuration proof
Package
@archpilotlabs/archpilot@0.2.10
Integrity
sha512-2V0WfNnvZVS/ey7ndKkhvYBI2YqIkrNTwkFmpMdjkMrb2RQuN7uDYCsOW2dVDPOqyf2q86V3gnc38i2jENGQOg==
Config hash
543EE6B120081ED1484974AF2AF9EEDA91976B0821671D29CB9EF5E5F8025922
Artifact hashes
architecture.json
543EE6B120081ED1484974AF2AF9EEDA91976B0821671D29CB9EF5E5F8025922
validation-status.json
56673E254CB861CD2086BB74D3440E087C99D4E1FCC2750C36287FA9D5E9F463
architecture-map.json
E52AB544689D168F790705B745B77E2DD8A943D7E2ED168E9478177AC2EBC69B
architecture-review-report.json
3D341D92A1FAEABBCB6886A4848ADAC9328A6312DB47723DCF31041737A74BA1

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.

Amplication Architecture Validation | ArchPilot