RepoPilot

juhaku/utoipa · Architecture

A static read of how juhaku/utoipa 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
120
Modules parsed
35 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.

  • utoipa-gen/tests/common.rs10 importers · radius 10
  • utoipa-actix-web/src/service_config.rs1 importers · radius 1
  • utoipa-actix-web/src/scope.rs1 importers · radius 1
  • utoipa-axum/src/router.rs1 importers · radius 1
  • utoipa-gen/src/component/features.rs1 importers · radius 1
  • utoipa-gen/src/component.rs1 importers · radius 1
  • utoipa-gen/src/doc_comment.rs1 importers · radius 1
  • utoipa-gen/src/ext.rs1 importers · radius 1

Modules (10)

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 juhaku/utoipa

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.