Which file should I inspect first in LangChain.js (libs/langchain-core)?

Start with src/messages/content. Run arc impact on that file before the change merges.

← Homepage All repository proof Validation record State of TS Architecture 2026

Repository proof

What ArcSight found in LangChain.js

Real arc impact on LangChain.js (libs/langchain-core) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?

Project: LangChain.js (libs/langchain-core) · Score: 66.4/100 (Moderate technical debt) · 248 modules · 973 edges

arc impact src/messages/content

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/messages/base24 dependents
src/messages/ai23 dependents
src/messages/content21 dependents
src/load/serializable15 dependents
src/messages/utils14 dependents
src/messages/block_translators12 dependents
src/messages/tool12 dependents
src/messages/block_translators/utils12 dependents

Blast radius, downstream modules

src/messages/content134 modules
src/load/serializable134 modules
src/messages/base131 modules
src/messages/ai131 modules
src/messages/utils131 modules
src/messages/block_translators131 modules
src/messages/tool131 modules
src/messages/message131 modules

Module	Fan-in	Blast	Risk
src/messages/content	21	134	CRITICAL
src/load/serializable	15	134	CRITICAL
src/messages/base	24	131	CRITICAL
src/messages/ai	23	131	CRITICAL
src/messages/utils	14	131	CRITICAL
src/messages/block_translators	12	131	CRITICAL
src/messages/tool	12	131	CRITICAL
src/messages/message	10	131	CRITICAL
src/errors	6	131	CRITICAL
src/messages/block_translators/utils	12		CRITICAL

What ArcSight found

src/messages/content: fan-in 21, blast radius 134, CRITICAL. 248 modules and 973 dependency edges traced.

Why it matters

In LangChain.js (libs/langchain-core), Change-risk signal at src/messages/content (fan-in 21) — merge impact can travel beyond the diff you see. Blast radius on src/messages/content reaches 134 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/messages/content
src/load/serializable
src/messages/base

What evidence supports it

Local CLI analysis — repository source stays on your machine
Structural coverage: 248 modules, 973 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 for this codebase — Dependency graph

Subsystem architecture for this codebase — Subsystem architecture

Architecture score & metrics

Score: 66.4/100 · Stability: 10/100 · Status: at_risk · Confidence: 100%

Dependency cycles: 88
Layer violations: 3
Duplicate authorities: 49

Architectural gravity centers

src/messages/content— concentrates too many responsibilities
src/messages/content— shared utility hub
src/load/serializable— concentrates too many responsibilities
src/load/serializable— shared utility hub
src/messages/base— concentrates too many responsibilities

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

LangChain.js (libs/langchain-core) architecture metrics

Score: 66.4
Modules: 248
Edges: 973

Metrics

Metric	Value
Architecture score	66.4/100
Modules	248
Edges	973
Dependency cycles	88

FAQ

What did ArcSight find in LangChain.js (libs/langchain-core)?: src/messages/content: fan-in 21, blast radius 134, CRITICAL. 248 modules and 973 dependency edges traced.
Why does the LangChain.js (libs/langchain-core) structure matter?: In LangChain.js (libs/langchain-core), Change-risk signal at src/messages/content (fan-in 21) — merge impact can travel beyond the diff you see. Blast radius on src/messages/content reaches 134 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 LangChain.js (libs/langchain-core)?: Start with src/messages/content. Run arc impact on that file before the change merges.

Key takeaways

•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/langchainjs/" width="320" height="180" frameborder="0"></iframe>

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