RepoPilot

suse/portus · Architecture

A static read of how suse/portus is wired together — module coupling, layering, and circular dependencies — derived from its import graph.

A
Architecture grade
score 99/100
0
Import cycles
lower is better
60
Modules parsed
29 edges
97%
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.

  • app/assets/javascripts/bootstrap.js2 importers · radius 2
  • app/assets/javascripts/polyfill.js2 importers · radius 2
  • app/assets/javascripts/modules/dashboard/index.js1 importers · radius 1
  • app/assets/javascripts/modules/users/pages/legacy/edit.js1 importers · radius 2
  • app/assets/javascripts/modules/users/unauthenticated.js1 importers · radius 1
  • app/assets/javascripts/modules/dashboard/pages/dashboard.js1 importers · radius 2
  • app/assets/javascripts/modules/explore/index.js1 importers · radius 1
  • app/assets/javascripts/modules/users/index.js1 importers · radius 1

Modules (7)

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

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.