Nested module discovery
The model captures 31 Java/Spring architecture areas across the repository.
Repository validation
Spring Modulith
A Java and Spring multi-module repository with core libraries, event integrations, observability modules, examples, and integration tests.
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.
Spring is a trademark of Broadcom Inc. and/or its subsidiaries.
See something inaccurate? Contact us.What ArchPilot found
31 architecture areas, 51 mapped relationships.
ArchPilot modeled Spring Modulith as a 31-component Maven reactor covering core libraries, event integrations, observability modules, examples, and integration-test modules.
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.
Source-backed architecture units
Mapped module dependencies
Blocking validation findings
Items for review, not confirmed defects
Dependency analysis covered 357 Java sources, but one supported source could not be fully analyzed.
- Analyzed sources
- 357
- Unsupported sources
- 1
Affected dependency-rule conclusions are surfaced as informational guidance rather than 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 alignment
Declared and detected dependency relationships align across many modules.
Partial dependency evidence
The one unsupported source is visible, and affected conclusions stay conservative.
Clean setup
No error-level findings and full readiness make the result easy to reproduce and inspect.
Findings
What deserves attention
27 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 hubs
Shared API and event modules have high inbound dependency counts.
Partial dependency evidence
One source-analysis gap makes affected dependency conclusions informational rather than definitive.
Published events
Examples and integration-test-style scope produce event review signals, not project defect claims.
Decision context
The generated governance model expects ADR context for dependency governance.
Confirmed architecture evidence
Many dependency relationships align
The preserved evidence shows declared and detected dependency relationships aligning across many modules.
Scope-dependent observation
Examples publish events without static handler evidence
AP-EVT-001 warnings include examples and integration-test-style scope. They are review signals, not project defect claims.
Dependency conclusions stay conservative
The AP-DEP guidance rows report 357 analyzed Java sources and one unsupported Java source, so affected dependency conclusions are informational.
How to interpret this validation
- Dependency analysis is partial because one supported-source file could not be fully analyzed.
- ArchPilot surfaces affected dependency-rule conclusions as informational guidance rather than pretending the analysis is complete.
- AP-EVT-001 warnings include examples and integration-test-style scope and must be read as review signals.
- AP-ARCH-012 passes.
- Warnings are not confirmed project defects. Many are heuristic or scope-dependent 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 fc0a547c05df 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
- spring-projects/spring-modulith
- Branch
- main
- Commit date
- 2026-08-20T22:51:19+02:00
- 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
99BC5231CC57F69764B2B928857432FCF6BD483380D71576DCCA938F0C35C634
Artifact hashes
- architecture.json
99BC5231CC57F69764B2B928857432FCF6BD483380D71576DCCA938F0C35C634- validation-status.json
7C884BF01138DFF5F1E5401394E771B7A6BE9DBCBE43D16D16E1DF3B7F8E3305- architecture-map.json
C8A5DA817337BA8FE69C982A697D51D8C941E455FD9E813066FB75192CE209B5- architecture-review-report.json
599C70A7BA410CC386E3FC8118A80DAD2F8437F729D977B8CED892EFAEB12367
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.