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

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowiseLAF-US/IDAHO-VAULT
ID
ID

LAF-US / IDAHO-VAULT

markdownmain0f65d4c867.8K linessynced 4h ago

Code health

9.2out of 10Excellent

This codebase scores 9.2 out of 10 on defect risk, which we rate excellent. It also scores maintainability 8.8 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: 26 of 37,084 files are git hotspots, and they average 3.2.

Full health report →
Documentation1,005pages0 with model-written prose, 1,005 built from the indexScore validation20/20639.38× baselineOf the 20 lowest-health files, 20 were bug-fixed in the last 6 months — 639.38× the 0% baselineDead code23exportsUnused exports that nothing in the graph reaches
Lines of code
867.8K
Files
37,084
Symbols
10,053
Modules
366
Languages
9

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Use uv.lock for dependency submission to avoid GitHub re-resolution failuresactive · 4h ago
  • Restore files damaged by over-broad redaction bugproposed · 4h ago
  • Use marker-based self-exclusion for git guard to avoid PATH recursion mismatchproposed · 4h ago
  • Replace broken chaining scripts with single correct chain_zettels.py toolproposed · 4h ago
  • Make chain_zettels.py --apply writes atomic via temp + fsync + os.replaceproposed · 4h ago
  • Exclude additional LEVELSET protocols and revert specified 100-series chainsproposed · 4h ago

Needs attention

53 open
  • high severity. Stale decisionUse uv.lock for dependency submission to avoid GitHub re-resolution failuresActive decision drifting from the code it governs
  • medium severity. ProposedRestore files damaged by over-broad redaction bugAuto-proposed decision awaiting review
  • medium severity. ProposedUse marker-based self-exclusion for git guard to avoid PATH recursion mismatchAuto-proposed decision awaiting review
  • medium severity. ProposedReplace broken chaining scripts with single correct chain_zettels.py toolAuto-proposed decision awaiting review
  • medium severity. ProposedMake chain_zettels.py --apply writes atomic via temp + fsync + os.replaceAuto-proposed decision awaiting review

Where the risk concentrates

All 26 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.6th22bug magnet4bus factor 197
classify_paths.py.github/scripts99.2th6bug magnet3bus factor 121
gh_cli.py.github/scripts98.8th4bug magnet2bus factor 127
dotfolder_reconcile.py98.3th2316
check_secret_patterns.py.github/scripts97.9th9bug magnet434

Composition

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

Explore this codebase

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