repowiserepowise
Sign in
2233admin/lazycodex
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowise2233admin/lazycodex
LA
LA

2233admin / lazycodex

markdownmain44aa8c4107.3K linessynced 1mo ago

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 9.6 and static performance risk 9.9 out of 10. The three are scored separately and never blended into one number. The files you change most are the weak spot: 93 of 929 files are git hotspots, and they average 7.6.

Full health report →
Score validation4/209.29× baselineOf the 20 lowest-health files, 4 were bug-fixed in the last 6 months — 9.29× the 2% baselineDead code24exportsUnused exports that nothing in the graph reaches
Lines of code
107.3K
Files
929
Symbols
2,895
Modules
109
Languages
9

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • Model routing is category-based with fallback chains to control quotaproposed
  • Fallback behavior when agent_type is unsupportedproposed
  • Install selectable multi-agent roles into ~/.codex/agents/ and pass agent_type to spawn_agentproposed
  • Use verified-completion loop with iteration caps for $ulw-loopproposed
  • Separate execution from planning: $start-work executes checklists and stops on completionproposed
  • Separate planning from code changes: $ulw-plan writes plans onlyproposed

Needs attention

47 open
  • medium severity. ProposedModel routing is category-based with fallback chains to control quotaAuto-proposed decision awaiting review
  • medium severity. ProposedFallback behavior when `agent_type` is unsupportedAuto-proposed decision awaiting review
  • medium severity. ProposedInstall selectable multi-agent roles into `~/.codex/agents/` and pass `agent_type` to `spawn_agent`Auto-proposed decision awaiting review
  • medium severity. ProposedUse verified-completion loop with iteration caps for `$ulw-loop`Auto-proposed decision awaiting review
  • medium severity. ProposedSeparate execution from planning: `$start-work` executes checklists and stops on completionAuto-proposed decision awaiting review

Where the risk concentrates

All 93 hotspots →

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

FileChurnPrior fixesMaintainersCommits 90d
cli.jsplugins/omo/components/bootstrap/dist99.9th02bus factor 18
cli.jsplugins/omo/components/codegraph/dist99.7th02bus factor 17
serve.jsplugins/omo/components/codegraph/dist99.6th01bus factor 16
index.jsplugins/omo/dist/cli-node99.4th01bus factor 15
index.jsplugins/omo/dist/cli99.3th01bus factor 15

Composition

Open the graph →
markdown 35%typescript 30%json 12%javascript 12%yaml 5%Other 7%

Explore this codebase

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