repowiserepowise
Sign in
LAF-US/IDAHO-VAULT
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
Chat
Stats
repowiserepowise
ExplorePricingDocs
Sign in
repowiseLAF-US/IDAHO-VAULT
ID
ID

LAF-US / IDAHO-VAULT

markdownmain827811e940.0K linessynced 2w ago
Since the previous index, 2w ago+1 file

Code health

9.3out of 10Excellent

This codebase scores 9.3 out of 10 on defect risk, which we rate excellent. It also scores maintainability 8.9 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: 24 of 37,363 files are git hotspots, and they average 3.4.

Full health report →
Documentation1,004pages0 with model-written prose, 1,004 built from the indexScore validation19/201075.6× baselineOf the 20 lowest-health files, 19 were bug-fixed in the last 6 months — 1075.6× the 0% baselineDead code14exportsUnused exports that nothing in the graph reaches
Lines of code
940.0K
Files
37,363
Symbols
9,998
Modules
380
Languages
9

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Submit dependencies from uv.lock instead of GitHub auto-submissionactive · 2w ago
  • Restore 12 files damaged by redaction bugproposed · 2w ago
  • Robust self-detection and wording for git guardrailsproposed · 2w ago
  • Replace broken chaining scripts with one correct, compiling toolproposed · 2w ago
  • Make chain_zettels.py --apply write atomicallyproposed · 2w ago
  • Exclude additional LEVELSET protocol files and revert 100-series chainsproposed · 2w ago

Needs attention

56 open
  • high severity. Stale decisionSubmit dependencies from uv.lock instead of GitHub auto-submissionActive decision drifting from the code it governs
  • medium severity. ProposedRestore 12 files damaged by redaction bugAuto-proposed decision awaiting review
  • medium severity. ProposedRobust self-detection and wording for git guardrailsAuto-proposed decision awaiting review
  • medium severity. ProposedReplace broken chaining scripts with one correct, compiling toolAuto-proposed decision awaiting review
  • medium severity. ProposedMake chain_zettels.py --apply write atomicallyAuto-proposed decision awaiting review

Where the risk concentrates

All 24 hotspots →

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

FileChurnPrior fixesMaintainersCommits 90d
review_feedback_loop.py.github/scripts99.6th29bug magnet5bus factor 1102
check_action_pins.py.github/scripts99.1th13bug magnet4bus factor 133
classify_paths.py.github/scripts98.7th6bug magnet3bus factor 121
gh_cli.py.github/scripts98.3th42bus factor 127
dotfolder_reconcile.py97.9th3419

Composition

Open the graph →
markdown 98%json 1%python 0%yaml 0%shell 0%Other 0%

Explore this codebase

  • Docs1,004 pages across 380 modules→
  • ChatAsk this codebase a question and get an answer with its sources→
  • Files37,363 files with per-file docs, health and history→
  • ArchitectureDependency graph, layers, and 33 entry points→
  • Code healthPer-file scores, 2,831 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→