open-telemetry/opentelemetry-js · Architecture
A static read of how open-telemetry/opentelemetry-js is wired together — module coupling, layering, and circular dependencies — derived from its import graph.
A
Architecture grade
score 92/100
1
Import cycles
lower is better
189
Modules parsed
246 edges
92%
Layeredness
clean-layer ratio
Most-depended-on modules
These are the highest-fan-in files — change them and the blast radius is largest. Read them first.
- api/src/context/types.ts14 importers · radius 35
- api/src/trace/span_context.ts7 importers · radius 32
- api/src/diag/types.ts7 importers · radius 26
- api/src/internal/global-utils.ts6 importers · radius 22
- api/src/trace/span.ts6 importers · radius 27
- api/src/api/diag.ts6 importers · radius 20
- api/src/trace/tracer.ts6 importers · radius 24
- experimental/packages/api-logs/src/types/Logger.ts6 importers · radius 8
Circular dependencies (1)
- experimental/packages/configuration/src/EnvReader.ts → experimental/packages/configuration/src/EnvDefinition.ts → experimental/packages/configuration/src/EnvReader.ts
Ask AI about open-telemetry/opentelemetry-js
Grounded in the actual source code. Pick a starter question or write your own.
What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.
Or write your own question →Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.