sherlock-project/sherlock · Architecture
A static read of how sherlock-project/sherlock 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
17
Modules parsed
17 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.
- sherlock_project/__init__.py5 importers · radius 8
- sherlock_project/result.py4 importers · radius 5
- sherlock_project/sherlock.py3 importers · radius 3
- sherlock_project/notify.py3 importers · radius 4
- sherlock_project/sites.py2 importers · radius 5
- tests/test_probes.py0 importers · radius 0
- tests/test_validate_targets.py0 importers · radius 0
- sherlock_project/__main__.py0 importers · radius 0
Ask AI about sherlock-project/sherlock
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.