Large dependency map
ArchPilot maps 103 architecture areas and 471 relationships.
Repository validation
Flowable
A large Java and Spring workflow engine repository with engine, REST, integration, and supporting modules.
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
103 architecture areas, 471 mapped relationships.
ArchPilot modeled Flowable as a large Java/Spring repository with 103 architecture areas and 471 mapped relationships.
The run is a strong large-scale Java dependency-map example with established dependency analysis and a visible API-detection caveat.
Source-backed architecture units
Mapped module dependencies
Blocking validation findings
Items for review, not confirmed defects
Dependency analysis was established for the preserved 0.2.10 validation evidence.
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.
Established dependency evidence
Dependency analysis is established for this run.
Review scale
Warnings and AP-DEP findings give reviewers a way to prioritize a large Java/Spring codebase.
Capability caveat
The page notes that REST controllers were present even though Smart Init persisted apiStyle: none.
Findings
What deserves attention
202 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
Established dependency analysis supports a large Java dependency map.
Ownership boundaries
Large domain and operation signals help reviewers inspect architecture areas.
Application and governance review signals
Warnings help reviewers prioritize without implying broad project defects.
Confirmed architecture evidence
Large Java dependency map
Flowable is published as a strong large-scale Java dependency-map example: 103 architecture areas and 471 mapped relationships.
Scope-dependent observation
API style needs manual interpretation
Smart Init persisted apiStyle: none despite Spring REST controllers being present. This is a capability caveat and should not be read as evidence about API absence.
How to interpret this validation
- Dependency analysis was established for this validation.
- Smart Init persisted apiStyle: none despite Spring REST controllers being present. This is an API-detection limitation, not evidence about API absence.
- Warnings are review signals against the generated model, not judgments on overall project quality.
- This is independent analysis of a public repository, not maintainer endorsement.
Reproduce and verify
Run from commit 53e93b6681e8 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
- flowable/flowable-engine
- Branch
- main
- Commit date
- 2026-08-21T20:09:44+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
5A238D7A33F7EBBE7DC89E1AD40143D260CDD1778A066D2C93204E1C62E6D0C2
Artifact hashes
- architecture.json
5A238D7A33F7EBBE7DC89E1AD40143D260CDD1778A066D2C93204E1C62E6D0C2- validation-status.json
8EA4919875B27950B21E8282CF259E891B129C9141C47668A5561BC5DE58CC16- architecture-map.json
9D2ED5D3D6792CBA844292E658E12A8DB0C0EE15990DB56A5A4ECC18E7B05077- architecture-review-report.json
BF1749AB89211518DE1D6786DF1FC60B86F1FD122FAAED90E462439BC64E2855
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.