Skip to main content
ArcSight

← HomepageAll repository proofValidation recordState of TS Architecture 2026

Repository proof

What ArcSight found in NocoDB

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

Project: NocoDB (packages/nocodb) · Score: 95.7/100 (Excellent architecture) · 1,095 modules · 489 edges

arc impact src/db/field-handler/handlers/decimal/decimal.general.handler

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/db/field-handler/handlers/decimal/decimal.general.handler7 dependents
  • src/db/util/Debug6 dependents
  • src/db/util/Result6 dependents
  • src/services/api-docs/swagger/getSwaggerColumnMetas6 dependents
  • src/services/api-docs/swaggerV2/getSwaggerColumnMetas6 dependents
  • src/services/api-docs/swaggerV3/getSwaggerColumnMetasV36 dependents
  • src/db/field-handler/handlers/number/number.general.handler5 dependents
  • src/types/nc-plugin/lib/XcPlugin5 dependents
Blast radius, downstream modules
  • src/db/field-handler/handlers/decimal/decimal.general.handler20 modules
  • src/db/field-handler/field-handler.interface10 modules
  • src/db/util/Debug9 modules
  • src/db/util/Result9 modules
  • src/services/api-docs/swagger/getSwaggerColumnMetas7 modules
  • src/services/api-docs/swaggerV2/getSwaggerColumnMetas7 modules
  • src/services/api-docs/swaggerV3/getSwaggerColumnMetasV37 modules
  • src/db/field-handler/handlers/number/number.general.handler5 modules
ModuleFan-inBlastRisk
src/db/field-handler/handlers/decimal/decimal.general.handler720LOW
src/db/field-handler/field-handler.interface410HIGH
src/db/util/Debug69HIGH
src/db/util/Result69HIGH
src/services/api-docs/swagger/getSwaggerColumnMetas67HIGH
src/services/api-docs/swaggerV2/getSwaggerColumnMetas67HIGH
src/services/api-docs/swaggerV3/getSwaggerColumnMetasV367HIGH
src/db/field-handler/handlers/number/number.general.handler55HIGH
src/types/nc-plugin/lib/XcPlugin55HIGH
src/db/sql-client/lib/KnexClient24HIGH
src/modules/jobs/jobs/at-import/engine/mockResponses14HIGH
src/db/field-handler/handlers/rating/rating.general.handler33HIGH
src/helpers/ncError23HIGH
src/db/sql-migrator/lib/KnexMigratorv213HIGH
src/modules/jobs/jobs/at-import/engine/mock13HIGH
src/db/CustomKnex4LOW
src/db/IBaseModelSqlV24LOW
src/db/cte-generator1LOW
src/db/field-handler/utils/handlerUtils1LOW

What ArcSight found

src/db/field-handler/handlers/decimal/decimal.general.handler: fan-in 7, blast radius 20, LOW. 1,095 modules and 489 dependency edges traced.

Why it matters

In NocoDB (packages/nocodb), Change-risk signal at src/db/field-handler/handlers/decimal/decimal.general.handler (fan-in 7) — merge impact can travel beyond the diff you see. Blast radius on src/db/field-handler/handlers/decimal/decimal.general.handler reaches 20 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/db/field-handler/handlers/decimal/decimal.general.handler
  • src/db/field-handler/field-handler.interface
  • src/db/util/Debug

What evidence supports it

  • Local CLI analysis — repository source stays on your machine
  • Structural coverage: 1,095 modules, 489 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: 95.7/100 · Stability: 64/100 · Status: healthy · Confidence: 100%

  • Dependency cycles: 1
  • Duplicate authorities: 65

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…) →

NocoDB (packages/nocodb) architecture metrics
Score
95.7
Modules
1,095
Edges
489

Metrics

MetricValue
Architecture score95.7/100
Modules1,095
Edges489
Dependency cycles1

FAQ

What did ArcSight find in NocoDB (packages/nocodb)?
src/db/field-handler/handlers/decimal/decimal.general.handler: fan-in 7, blast radius 20, LOW. 1,095 modules and 489 dependency edges traced.
Why does the NocoDB (packages/nocodb) structure matter?
In NocoDB (packages/nocodb), Change-risk signal at src/db/field-handler/handlers/decimal/decimal.general.handler (fan-in 7) — merge impact can travel beyond the diff you see. Blast radius on src/db/field-handler/handlers/decimal/decimal.general.handler reaches 20 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 NocoDB (packages/nocodb)?
Start with src/db/field-handler/handlers/decimal/decimal.general.handler. Run arc impact on that file before the change merges.

Key takeaways

  • •Architecture score 95.7/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/nocodb/" width="320" height="180" frameborder="0"></iframe>

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