RepoPilot

turbot/steampipe · Architecture

A static read of how turbot/steampipe 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
287
Modules parsed
346 edges
99%
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.

  • pkg/constants/app.go88 importers · radius 105
  • pkg/db/db_common/acquire_session_result.go39 importers · radius 42
  • pkg/error_helpers/cancelled.go33 importers · radius 72
  • pkg/filepaths/db_path.go25 importers · radius 37
  • pkg/steampipeconfig/connection_plugin.go23 importers · radius 32
  • pkg/statushooks/context.go20 importers · radius 23
  • pkg/pluginmanager_service/grpc/proto/plugin_manager.pb.go15 importers · radius 47
  • pkg/cmdconfig/app_specific.go13 importers · radius 13

Modules (23)

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 turbot/steampipe

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.