Code health

Route: /code-health

Scenario: Your mobile CI posts bundle KB and god-file LOC on every push to main. You want one console view that shows whether the app is getting heavier or sprouting unmaintainable files — without opening GitHub Actions logs.

This page reads only — it never triggers a scan. Data arrives via POST /v1/ingest/metrics from your repo’s CI workflow.

What you see

Section	Source
Summary scorecard	Error/warn finding count, max LOC, latest bundle KB
Bundle-size trends	Sparkline per `bundle.*` metric from `metric_series`
God-file findings	Files over the LOC budget (`code_health.*` gate)

Wiring CI ingest

Mint an SDK ingest key on Projects.
Add repo secrets: MUSHI_API_URL, MUSHI_INGEST_KEY.
Post on every main push:


- name: Mushi code health ingest
  run: node scripts/scan-god-files.mjs && node scripts/post-metrics.mjs
  env:
    MUSHI_API_URL: ${{ secrets.MUSHI_API_URL }}
    MUSHI_INGEST_KEY: ${{ secrets.MUSHI_INGEST_KEY }}

Reference implementation: kensaurus/yen-yen — .github/workflows/bundle-budget.yml

scripts/scan-god-files.mjs.

API


GET /v1/admin/code-health?project_id=<uuid>
POST /v1/ingest/metrics   # CI push — apiKeyAuth, prefix allow-list bundle.* / code_health.*

Full-stack audit — DB advisors + gate runs (push-button)
Drift scanner — schema drift vs previous snapshot
Connect — wire GitHub + CI secrets in one place

Code health

What you see

Wiring CI ingest

API

Related pages