What ArcSight found
src/auth/verifiers/common: fan-in 9, blast radius 10, LOW. 31 modules and 42 dependency edges traced.
← HomepageAll repository proofValidation recordState of TS Architecture 2026
Repository proof
What ArcSight found in RedwoodJS
Real arc impact on RedwoodJS (packages/api) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?
Project: RedwoodJS (packages/api) · Score: 95.3/100 (Excellent architecture) · 31 modules · 42 edges
arc impact src/auth/verifiers/commonRun the same analysis on your repository in under 3 minutes.
Proof summary
Four questions every public repository page must answer — see validation record.
Modules to inspect
One row per module. Fan-in is direct dependents. Blast radius is downstream modules reachable from that file.
- src/auth/verifiers/common9 dependents
- src/cache/clients/BaseClient4 dependents
- src/auth/verifiers/base64Sha1Verifier1 dependents
- src/auth/verifiers/base64Sha256Verifier1 dependents
- src/auth/verifiers/jwtVerifier1 dependents
- src/auth/verifiers/secretKeyVerifier1 dependents
- src/auth/verifiers/sha1Verifier1 dependents
- src/auth/verifiers/sha256Verifier1 dependents
- src/auth/verifiers/common10 modules
- src/auth/verifiers/base64Sha1Verifier10 modules
- src/auth/verifiers/base64Sha256Verifier10 modules
- src/auth/verifiers/jwtVerifier10 modules
- src/auth/verifiers/secretKeyVerifier10 modules
- src/auth/verifiers/sha1Verifier10 modules
- src/auth/verifiers/sha256Verifier10 modules
- src/auth/verifiers/skipVerifier10 modules
| Module | Fan-in | Blast | Risk |
|---|---|---|---|
| src/auth/verifiers/common | 9 | 10 | LOW |
| src/auth/verifiers/base64Sha1Verifier | 1 | 10 | LOW |
| src/auth/verifiers/base64Sha256Verifier | 1 | 10 | LOW |
| src/auth/verifiers/jwtVerifier | 1 | 10 | LOW |
| src/auth/verifiers/secretKeyVerifier | 1 | 10 | LOW |
| src/auth/verifiers/sha1Verifier | 1 | 10 | HIGH |
| src/auth/verifiers/sha256Verifier | 1 | 10 | HIGH |
| src/auth/verifiers/skipVerifier | 1 | 10 | HIGH |
| src/auth/verifiers/timestampSchemeVerifier | 1 | 10 | HIGH |
| src/cache/clients/BaseClient | 4 | 4 | CRITICAL |
Why it matters
In RedwoodJS (packages/api), Change-risk signal at src/auth/verifiers/common (fan-in 9) — merge impact can travel beyond the diff you see. Blast radius on src/auth/verifiers/common reaches 10 downstream modules. ArcSight answers “what breaks if I change this?” before you ship; high fan-in is a change-risk signal, not a verdict on design quality.
What we'd inspect first
- src/auth/verifiers/common
- src/auth/verifiers/base64Sha1Verifier
- src/auth/verifiers/base64Sha256Verifier
What evidence supports it
- Local CLI analysis — repository source stays on your machine
- Structural coverage: 31 modules, 42 edges in this snapshot
- Reproducible fields match homepage live demo and frozen proof output
Architectural Risk Map
Where risk accumulates by control surface — drill down Surface → Substrate → Mechanism → Evidence.
See control surfaces →Dependency evidence
Architecture visualization
Diagrams are generated from ArcSight analysis data. Dependency graph and risk map show key modules; subsystem view shows high-level structure.
Architecture score & metrics
Score: 95.3/100 · Stability: 51/100 · Status: healthy · Confidence: 100%
- Dependency cycles: 8
CLI workflow
Impact, then scan, fix, finish, and watch.
arc impact <file>See what a change breaksarc scanFind issuesarc fixApply fixesarc finishResolve remainingarc watchKeep clean
- Score
- 95.3
- Modules
- 31
- Edges
- 42
Metrics
| Metric | Value |
|---|---|
| Architecture score | 95.3/100 |
| Modules | 31 |
| Edges | 42 |
| Dependency cycles | 8 |
FAQ
- What did ArcSight find in RedwoodJS (packages/api)?
- src/auth/verifiers/common: fan-in 9, blast radius 10, LOW. 31 modules and 42 dependency edges traced.
- Why does the RedwoodJS (packages/api) structure matter?
- In RedwoodJS (packages/api), Change-risk signal at src/auth/verifiers/common (fan-in 9) — merge impact can travel beyond the diff you see. Blast radius on src/auth/verifiers/common reaches 10 downstream modules. ArcSight answers “what breaks if I change this?” before you ship; high fan-in is a change-risk signal, not a verdict on design quality.
- Which file should I inspect first in RedwoodJS (packages/api)?
- Start with src/auth/verifiers/common. Run arc impact on that file before the change merges.
Key takeaways
- •Architecture score 95.3/100 indicates a healthy structure with room to reduce cycles and violations.
- •Structural scan reports dependency cycles — inspect impact paths before refactors that cross module boundaries.
- •High fan-in modules are change-risk zones; run
arc explain <path>before refactoring. - •Run the full workflow (analyze, hotspots, explain, impact, snapshot, drift) in your repo for deterministic architecture insights.
Run ArcSight on your repo
Install locally, then run arc impact on the file you plan to change — before merge.
Embed this report
Use this iframe to show the architecture badge on your site.
<iframe src="https://arcsight.ai/embed/redwoodjs/" width="320" height="180" frameborder="0"></iframe>Evidence-backed analysis snapshot. Validation record · Install · Homepage demo