RepoPilot

greptimeteam/greptimedb · Architecture

A static read of how greptimeteam/greptimedb 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
400
Modules parsed
151 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.

  • src/cli/src/metadata.rs2 importers · radius 2
  • src/api/src/helper.rs2 importers · radius 2
  • src/cli/src/utils.rs2 importers · radius 3
  • src/common/datasource/src/tests.rs2 importers · radius 2
  • src/common/mem-prof/src/error.rs2 importers · radius 2
  • src/cmd/src/bin/query_regression_runner/remote/mod.rs1 importers · radius 1
  • src/api/src/v1.rs1 importers · radius 1
  • src/cli/src/bench.rs1 importers · radius 1

Modules (24)

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 greptimeteam/greptimedb

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.