RepoPilot

google/wire · Architecture

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

B
Architecture grade
score 84/100
0
Import cycles
lower is better
207
Modules parsed
92 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.

  • wire.go91 importers · radius 91
  • internal/wire/analyze.go1 importers · radius 1
  • internal/wire/testdata/BindInjectorArg/foo/wire.go0 importers · radius 0
  • internal/wire/testdata/BindInjectorArgPointer/foo/wire.go0 importers · radius 0
  • internal/wire/testdata/BindInterfaceWithValue/foo/wire.go0 importers · radius 0
  • internal/wire/testdata/BuildTagsAllPackages/bar/bar.go0 importers · radius 0
  • internal/wire/testdata/BuildTagsAllPackages/bar/bar_inject.go0 importers · radius 0
  • internal/wire/testdata/BuildTagsAllPackages/foo/wire.go0 importers · radius 0

Modules (17)

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.