projectdiscovery/naabu · Architecture
A static read of how projectdiscovery/naabu 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
124
Modules parsed
117 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.
- pkg/port/port.go26 importers · radius 35
- pkg/protocol/protocol.go22 importers · radius 37
- pkg/scan/arp.go17 importers · radius 20
- pkg/result/results.go15 importers · radius 15
- pkg/privileges/privileges.go11 importers · radius 13
- pkg/fingerprint/engine.go7 importers · radius 7
- pkg/routing/gateway_ip.go5 importers · radius 5
- internal/testutils/integration.go4 importers · radius 4
Modules (6)
Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.
- pkg/scan11 files · 17 in-degree
- pkg/result2 files · 15 in-degree
- pkg/fingerprint2 files · 7 in-degree
- pkg/runner31 files · 3 in-degree
- internal/pdcp2 files · 1 in-degree
- cmd/integration-test3 files · 0 in-degree
Ask AI about projectdiscovery/naabu
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.