imputnet/helium · Architecture
A static read of how imputnet/helium is wired together — module coupling, layering, and circular dependencies — derived from its import graph.
A
Architecture grade
score 100/100
0
Import cycles
lower is better
52
Modules parsed
5 edges
100%
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.
- utils/__init__.py2 importers · radius 2
- devutils/third_party/unidiff/patch.py1 importers · radius 1
- devutils/third_party/unidiff/constants.py1 importers · radius 2
- devutils/third_party/unidiff/errors.py1 importers · radius 2
- devutils/third_party/unidiff/__init__.py0 importers · radius 0
- utils/tests/test_domain_substitution.py0 importers · radius 0
- utils/tests/test_patches.py0 importers · radius 0
Modules (2)
Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.
- devutils/third_party/unidiff4 files · 3 in-degree
- utils/tests2 files · 0 in-degree
Ask AI about imputnet/helium
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 questionInformational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.