RepoPilot

future-architect/vuls · Architecture

A static read of how future-architect/vuls 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
178
Modules parsed
328 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.

  • models/cvecontents.go78 importers · radius 87
  • config/awsconf.go72 importers · radius 78
  • logging/logutil.go50 importers · radius 61
  • constant/constant.go39 importers · radius 101
  • util/util.go16 importers · radius 21
  • reporter/azureblob.go8 importers · radius 9
  • contrib/snmp2cpe/pkg/snmp/snmp.go6 importers · radius 8
  • detector/detector.go4 importers · radius 5

Modules (14)

Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.

Ask AI about future-architect/vuls

Grounded in the actual source code. Pick a starter question or write your own.

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.