repowiserepowise
Sign in
coral-protocol/coral-server
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowisecoral-protocol/coral-server
CO
CO

coral-protocol / coral-server

kotlinmaster9151ac321.9K linessynced 1mo ago

Code health

7.1out of 10Good

This codebase scores 7.1 out of 10 on defect risk, which we rate good. It also scores maintainability 8.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: 29 of 254 files are git hotspots, and they average 4.7.

Full health report →
Score validation12/203.72× baselineOf the 20 lowest-health files, 12 were bug-fixed in the last 6 months — 3.72× the 16% baselineDead code90exportsUnused exports that nothing in the graph reaches
Lines of code
21.9K
Files
254
Symbols
3,856
Modules
29
Languages
6

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • NOTE: The values in this file are asserted in tests!proposed
  • A test MCP that can be used for testing prototype runtimes toolServer configuration. Note that SSE iproposed
  • This performs a basic test where one agent is tasked to ask another to be given a piece of data thatproposed
  • agent1 should have no reliance on agent3 because their common link is non-blockingproposed
  • block because agent2 doesn't connectproposed
  • even though agent1 is only blocked by agent2, this should time out because agent3 never connectsproposed

Needs attention

93 open
  • medium severity. ProposedNOTE: The values in this file are asserted in tests!Auto-proposed decision awaiting review
  • medium severity. ProposedA test MCP that can be used for testing prototype runtimes toolServer configuration. Note that SSE iAuto-proposed decision awaiting review
  • medium severity. ProposedThis performs a basic test where one agent is tasked to ask another to be given a piece of data thatAuto-proposed decision awaiting review
  • medium severity. Proposedagent1 should have no reliance on agent3 because their common link is non-blockingAuto-proposed decision awaiting review
  • medium severity. Proposedblock because agent2 doesn't connectAuto-proposed decision awaiting review

Where the risk concentrates

All 29 hotspots →

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

FileChurnPrior fixesMaintainersCommits 90d
RegistryAgentTest.ktsrc/test/kotlin/org/coralprotocol/coralserver/registry99.6th327
SessionApiTest.ktsrc/test/kotlin/org/coralprotocol/coralserver/session99.1th23bus factor 13
AgentOption.ktsrc/main/kotlin/org/coralprotocol/coralserver/agent/registry/option98.7th124
SessionTest.ktsrc/test/kotlin/org/coralprotocol/coralserver/session98.3th043
SessionAgent.ktsrc/main/kotlin/org/coralprotocol/coralserver/session97.9th037

Composition

Open the graph →
kotlin 93%markdown 2%yaml 2%toml 2%json 1%Other 0%

Explore this codebase

  • Docs0 pages across 29 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files254 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 1 entry points→
  • Code healthPer-file scores, 411 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→