repowiserepowise
Sign in
11philip22/guerrillamail-client-cpp
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowise11philip22/guerrillamail-client-cpp
GU
GU

11philip22 / guerrillamail-client-cpp

cppmasterf630f531.3K linessynced 5h ago

Code health

8.2out of 10Excellent

This codebase scores 8.2 out of 10 on defect risk, which we rate excellent. It also scores maintainability 9.6 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: 3 of 16 files are git hotspots, and they average 7.5.

Full health report →
Documentation29pages0 with model-written prose, 29 built from the index
Lines of code
1.3K
Files
16
Symbols
117
Modules
3
Languages
3

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Mirror upstream attachment metadata schemaproposed · 5h ago

Needs attention

14 open
  • medium severity. ProposedMirror upstream attachment metadata schemaAuto-proposed decision awaiting review
  • medium severity. Ungovernedsrc/client.cppHigh-churn file with no governing decision
  • medium severity. Ungovernedsrc/protocol/requests.cppHigh-churn file with no governing decision
  • medium severity. Ungovernedsrc/transport/curl_session.cppHigh-churn file with no governing decision
  • medium severity. Knowledge siloexamples/basic_flow.cpp100% single-owner concentration

Where the risk concentrates

All 3 hotspots →

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

FileChurnPrior fixesMaintainersCommits 90d
requests.cppsrc/protocol92.9th01bus factor 15
curl_session.cppsrc/transport85.7th11bus factor 13
client.cppsrc78.6th01bus factor 15

Composition

Open the graph →
cpp 88%markdown 6%json 6%

Explore this codebase

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