repowiserepowise
Sign in
kaizakin/siphon
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowisekaizakin/siphon
SI
SI

kaizakin / siphon

gomain6d657461.6K linessynced 1mo ago

Code health

9.0out of 10Excellent

This codebase scores 9.0 out of 10 on defect risk, which we rate excellent. It also scores maintainability 9.8 and static performance risk 10.0 out of 10. The three are scored separately and never blended into one number. The files you change most are the weak spot: 6 of 30 files are git hotspots, and they average 7.0.

Full health report →
Score validation7/201.5× baselineOf the 20 lowest-health files, 7 were bug-fixed in the last 6 months — 1.5× the 23% baselineDead code10exportsUnused exports that nothing in the graph reaches
Lines of code
1.6K
Files
30
Symbols
73
Modules
13
Languages
5

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • ingestevent sends an optimistic acknowledgement as soon as the event reaches the buffered channel…proposed · 1mo ago
  • protojson instead of json because a protoc generated struct is being serialized here protojson is…proposed · 1mo ago
  • If the following call panics, it indicates UnimplementedEventIngestionServiceServer was embedded by…proposed · 1mo ago
  • UnimplementedEventIngestionServiceServer must be embedded to have forward compatible…proposed · 1mo ago
  • Optimistically acknowledge ingestion events upon bufferingproposed · 1mo ago
  • Use protojson for serializing protoc-generated structsproposed · 1mo ago

Needs attention

43 open
  • medium severity. Proposedingestevent sends an optimistic acknowledgement as soon as the event reaches the buffered channel…Auto-proposed decision awaiting review
  • medium severity. Proposedprotojson instead of json because a protoc generated struct is being serialized here protojson is…Auto-proposed decision awaiting review
  • medium severity. ProposedIf the following call panics, it indicates UnimplementedEventIngestionServiceServer was embedded by…Auto-proposed decision awaiting review
  • medium severity. ProposedUnimplementedEventIngestionServiceServer must be embedded to have forward compatible…Auto-proposed decision awaiting review
  • medium severity. ProposedOptimistically acknowledge ingestion events upon bufferingAuto-proposed decision awaiting review

Where the risk concentrates

All 6 hotspots →

Ranked by prior bug fixes and change frequency, mined from full git history rather than from the code alone.

FileChurnPrior fixesMaintainersCommits 90d
ingestion.pb.gogen/ingestion/v196.4th01bus factor 13
handlers.gointernal/auth/handlers92.9th11bus factor 110
ingestion_server.gointernal/ingestion/grpc89.3th21bus factor 16
query.sql.gointernal/auth/sqlc82.1th11bus factor 14
event.gointernal/gateway/handlers78.6th11bus factor 14

Composition

Open the graph →
go 67%sql 17%yaml 10%markdown 3%proto 3%

Explore this codebase

  • Docs0 pages across 13 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files30 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 4 entry points→
  • Code healthPer-file scores, 21 open findings, coverage and refactoring targets→
  • Knowledge graphEntities, communities, and the paths between them→
  • Change couplingFiles that keep changing together, mined from commit history→
  • CommitsChange-risk ranked history with agent provenance→
  • ContributorsBus factor, per-file maintainers, and the human/agent split→
  • StatsSize class, origin, lifetime churn, rhythm and records→
  • CostsWhat indexing this snapshot cost, by model and by run→