repowiserepowise
Sign in
veerbhadramahant/memory-manager-iiit-hc
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiseveerbhadramahant/memory-manager-iiit-hc
ME
ME

veerbhadramahant / memory-manager-iiit-hc

typescriptmaind55e3c212.6K linessynced 21h ago

Code health

8.3out of 10Excellent

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

Full health report →
Documentation97pages0 with model-written prose, 97 built from the indexDead code6exportsUnused exports that nothing in the graph reaches
Lines of code
12.6K
Files
81
Symbols
412
Modules
23
Languages
8

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Runtime model switching across three providers, shared memory (D32)proposed · 21h ago
  • Make fallback block non-private and route uncertain classifier output thereproposed · 21h ago
  • Report withheld private count instead of relying on documentation claimsproposed · 21h ago
  • Implement privacy by excluding private blocks from retrieval SQLproposed · 21h ago
  • Separate privacy from scope in memory handlingproposed · 21h ago
  • Deterministic graph layout via sorted node insertionproposed · 21h ago

Needs attention

36 open
  • medium severity. ProposedRuntime model switching across three providers, shared memory (D32)Auto-proposed decision awaiting review
  • medium severity. ProposedMake fallback block non-private and route uncertain classifier output thereAuto-proposed decision awaiting review
  • medium severity. ProposedReport withheld private count instead of relying on documentation claimsAuto-proposed decision awaiting review
  • medium severity. ProposedImplement privacy by excluding private blocks from retrieval SQLAuto-proposed decision awaiting review
  • medium severity. ProposedSeparate privacy from scope in memory handlingAuto-proposed decision awaiting review

Where the risk concentrates

All 11 hotspots →

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

FileChurnPrior fixesMaintainersCommits 90d
page.tsxfrontend/app98.3th12bus factor 110
MemoryGraph.tsxfrontend/components96.6th024
memory.pybackend/app/routers94.9th027
ReviewCard.tsxfrontend/components93.2th01bus factor 15
graph-layout.tsfrontend/lib91.5th023

Composition

Open the graph →
typescript 42%python 26%markdown 14%sql 10%json 4%Other 5%

Explore this codebase

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