Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in Strapi

Real arc impact on Strapi (packages/core/strapi) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?

Project: Strapi (packages/core/strapi) · Score: 94.4/100 (Excellent architecture) · 78 modules · 194 edges

arc impact src/cli/utils/logger
Install ArcSight →Why trust ArcSight →

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

Fan-in, direct dependents
  • src/cli/types35 dependents
  • src/cli/utils/helpers32 dependents
  • src/node/create-build-context10 dependents
  • src/cli/utils/get-inquirer9 dependents
  • src/cli/utils/logger7 dependents
  • src/node/core/files4 dependents
  • src/node/core/errors4 dependents
  • src/cli/utils/tsconfig2 dependents
Blast radius, downstream modules
  • src/cli/utils/logger51 modules
  • src/cli/utils/tsconfig47 modules
  • src/cli/types46 modules
  • src/cli/utils/get-inquirer36 modules
  • src/cli/utils/helpers35 modules
  • src/node/core/files20 modules
  • src/node/core/errors19 modules
  • src/node/create-build-context18 modules
ModuleFan-inBlastRisk
src/cli/utils/logger751MEDIUM
src/cli/utils/tsconfig247MEDIUM
src/cli/types3546HIGH
src/cli/utils/get-inquirer936MEDIUM
src/cli/utils/helpers3235MEDIUM
src/node/core/files420CRITICAL
src/node/core/errors419CRITICAL
src/node/create-build-context1018CRITICAL

What ArcSight found

src/cli/utils/logger: fan-in 7, blast radius 51, MEDIUM. 78 modules and 194 dependency edges traced.

Why it matters

In Strapi (packages/core/strapi), Change-risk signal at src/cli/utils/logger (fan-in 7) — merge impact can travel beyond the diff you see. Blast radius on src/cli/utils/logger reaches 51 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/cli/utils/logger
  • src/cli/utils/tsconfig
  • src/cli/types

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 78 modules, 194 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.

Dependency graph
Dependency graph for this codebase
Subsystem architecture
Subsystem architecture for this codebase
Risk map
Risk map for this codebase

Architecture score & metrics

Score: 94.4/100 · Stability: 45/100 · Status: healthy · Confidence: 100%

  • Dependency cycles: 1
  • Layer violations: 2
  • Duplicate authorities: 3

Architectural gravity centers

  • src/cli/utils/logger— concentrates too many responsibilities
  • src/cli/utils/logger— crosses a layer boundary
  • src/cli/types— concentrates too many responsibilities
  • src/cli/types— shared utility hub
  • src/cli/types— crosses a layer boundary

CLI workflow

Impact, then scan, fix, finish, and watch.

  • arc impact <file>See what a change breaks
  • arc scanFind issues
  • arc fixApply fixes
  • arc finishResolve remaining
  • arc watchKeep clean

More commands (explain, guard…) →

Strapi (packages/core/strapi) architecture metrics
Score
94.4
Modules
78
Edges
194

Metrics

MetricValue
Architecture score94.4/100
Modules78
Edges194
Dependency cycles1

FAQ

What did ArcSight find in Strapi (packages/core/strapi)?
src/cli/utils/logger: fan-in 7, blast radius 51, MEDIUM. 78 modules and 194 dependency edges traced.
Why does the Strapi (packages/core/strapi) structure matter?
In Strapi (packages/core/strapi), Change-risk signal at src/cli/utils/logger (fan-in 7) — merge impact can travel beyond the diff you see. Blast radius on src/cli/utils/logger reaches 51 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 Strapi (packages/core/strapi)?
Start with src/cli/utils/logger. Run arc impact on that file before the change merges.

Key takeaways

  • •Architecture score 94.4/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.

npm install -g arcsight
arc impact <path>
Install ArcSight →

Embed this report

Use this iframe to show the architecture badge on your site.

<iframe src="https://arcsight.ai/embed/strapi/" width="320" height="180" frameborder="0"></iframe>

Evidence-backed analysis snapshot. Validation record · Install · Homepage demo