RepoPilot

servo/webrender · Architecture

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

A
Architecture grade
score 98/100
0
Import cycles
lower is better
133
Modules parsed
105 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.

  • webrender/src/prim_store/mod.rs1 importers · radius 1
  • webrender/src/renderer/mod.rs1 importers · radius 1
  • webrender/src/prim_store/gradient/mod.rs1 importers · radius 2
  • webrender/src/device/mod.rs1 importers · radius 1
  • webrender/src/compositor/mod.rs1 importers · radius 1
  • webrender/src/texture_pack/mod.rs1 importers · radius 1
  • glsl-to-cxx/src/hir.rs1 importers · radius 1
  • peek-poke/src/slice_ext.rs1 importers · radius 1

Modules (13)

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 servo/webrender

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.