iptv-org/iptv · Architecture
A static read of how iptv-org/iptv is wired together — module coupling, layering, and circular dependencies — derived from its import graph.
B
Architecture grade
score 78/100
4
Import cycles
lower is better
52
Modules parsed
141 edges
96%
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.
- scripts/constants.ts28 importers · radius 38
- scripts/models/index.ts24 importers · radius 35
- scripts/core/index.ts17 importers · radius 35
- scripts/api.ts15 importers · radius 37
- scripts/generators/generator.ts12 importers · radius 14
- scripts/utils.ts6 importers · radius 35
- scripts/tables/table.ts4 importers · radius 6
- scripts/core/streamTester.ts2 importers · radius 35
Circular dependencies (4)
- scripts/models/index.ts → scripts/models/issue.ts → scripts/core/index.ts → scripts/core/playlistParser.ts → scripts/models/index.ts
- scripts/models/index.ts → scripts/models/issue.ts → scripts/core/index.ts → scripts/core/streamTester.ts → scripts/models/index.ts
- scripts/models/index.ts → scripts/models/playlist.ts → scripts/models/index.ts
- scripts/models/index.ts → scripts/models/stream.ts → scripts/utils.ts → scripts/models/index.ts
Ask AI about iptv-org/iptv
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.