RepoPilot

pydantic/monty · Architecture

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

A
Architecture grade
score 87/100
0
Import cycles
lower is better
400
Modules parsed
203 edges
98%
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.

  • crates/monty-proto/src/convert/mod.rs2 importers · radius 3
  • crates/monty/src/types/mod.rs1 importers · radius 1
  • crates/monty/src/builtins/mod.rs1 importers · radius 1
  • crates/monty/src/types/itertools/mod.rs1 importers · radius 2
  • crates/monty/src/bytecode/vm/mod.rs1 importers · radius 2
  • crates/monty/src/bytecode/mod.rs1 importers · radius 1
  • crates/monty-proto/src/python/mod.rs1 importers · radius 1
  • crates/monty/src/args/mod.rs1 importers · radius 1

Modules (22)

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 pydantic/monty

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.