repowiserepowise
Sign in
christensenjairus/vicegerent-agents
OverviewDocsArchitectureKnowledge GraphFilesCode HealthRefactoring

People & History

CommitsContributorsDecisions
ChatPro
Stats
repowiserepowise
ExplorePricingDocs
Sign inIndex repoIndex your repo free
repowisechristensenjairus/vicegerent-agents
VI
VI

christensenjairus / vicegerent-agents

yamlmain38d789c20.4K linessynced 1mo ago

Code health

8.8out of 10Excellent

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

Full health report →
Score validation6/207.91× baselineOf the 20 lowest-health files, 6 were bug-fixed in the last 6 months — 7.91× the 4% baselineDead code10exportsUnused exports that nothing in the graph reaches
Lines of code
20.4K
Files
211
Symbols
312
Modules
50
Languages
11

Recent activity

All commits →

Commits

No commits indexed yet.

Decisions

  • MCP authorization layering: gateway allowlist is the single tool gateproposed
  • Flux-generated manifests excluded from yamlfixproposed
  • Secrets management via 1Password Connect with least-privilege scopingproposed
  • No vendor directories; pull controller charts via Fluxproposed
  • Documentation-driven layout via copy-based scaffoldingproposed
  • Repository directory ownership conventionsproposed

Needs attention

48 open
  • medium severity. ProposedMCP authorization layering: gateway allowlist is the single tool gateAuto-proposed decision awaiting review
  • medium severity. ProposedFlux-generated manifests excluded from yamlfixAuto-proposed decision awaiting review
  • medium severity. ProposedSecrets management via 1Password Connect with least-privilege scopingAuto-proposed decision awaiting review
  • medium severity. ProposedNo vendor directories; pull controller charts via FluxAuto-proposed decision awaiting review
  • medium severity. ProposedDocumentation-driven layout via copy-based scaffoldingAuto-proposed decision awaiting review

Where the risk concentrates

All 4 hotspots →

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

FileChurnPrior fixesMaintainersCommits 90d
vicegerent_mcp.pyhost/mcp97.5th43bus factor 116
setup-secrets.shscripts/install95.0th6422
validate.shscripts92.5th034
test-mcp-policies.shscripts90.0th225

Composition

Open the graph →
yaml 70%shell 6%markdown 5%go 5%typescript 3%Other 10%

Explore this codebase

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