repowiserepowise
Sign in
rishi-3161/smart-expense-tracker-api
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiserishi-3161/smart-expense-tracker-api
SM
SM

rishi-3161 / smart-expense-tracker-api

pythonmaster2222ba8936 linessynced 22h ago

Code health

9.5out of 10Excellent

This codebase scores 9.5 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: 2 of 12 files are git hotspots, and they average 8.7.

Full health report →
Documentation22pages0 with model-written prose, 22 built from the index
Lines of code
936
Files
12
Symbols
93
Modules
3
Languages
4

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

No decisions extracted yet.

Needs attention

10 open
  • medium severity. Ungovernedsrc/storage.pyHigh-churn file with no governing decision
  • medium severity. Ungovernedtests/test_api.pyHigh-churn file with no governing decision
  • medium severity. Knowledge silosrc/main.py100% single-owner concentration
  • medium severity. Knowledge silosrc/models.py100% single-owner concentration
  • medium severity. Knowledge silosrc/routes.py100% single-owner concentration

Where the risk concentrates

All 2 hotspots →

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

FileChurnPrior fixesMaintainersCommits 90d
test_api.pytests87.5th01bus factor 13
storage.pysrc75.0th01bus factor 13

Composition

Open the graph →
python 67%markdown 17%dockerfile 8%yaml 8%

Explore this codebase

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