RepoPilot

eventual-inc/daft · Architecture

A static read of how eventual-inc/daft is wired together — module coupling, layering, and circular dependencies — derived from its import graph.

A
Architecture grade
score 97/100
0
Import cycles
lower is better
400
Modules parsed
339 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.

  • src/daft-dashboard/frontend/src/app/query/types.ts6 importers · radius 7
  • src/daft-dashboard/frontend/src/app/query/stats-utils.tsx4 importers · radius 5
  • src/daft-dashboard/frontend/src/app/query/tree-colors.ts3 importers · radius 4
  • src/daft-core/src/series/ops/logical.rs2 importers · radius 4
  • src/daft-dashboard/frontend/src/app/query/tree-layout.tsx2 importers · radius 3
  • src/daft-dashboard/frontend/src/components/notifications-provider.tsx2 importers · radius 4
  • src/daft-core/src/array/ops/mod.rs1 importers · radius 2
  • src/daft-core/src/series/ops/mod.rs1 importers · radius 2

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 eventual-inc/daft

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.