Health Reports

Health Reports give your team ongoing visibility into codebase health — dependencies, bundle size, unused code, and security findings — without digging through dashboards.

How it works

Your CI pipeline collects health metrics via the dev-herald/health action (or the ingest API for custom integrations)
Dev Herald stores the report and compares it against the previous snapshot
If Slack is connected, a summary is posted to your subscribed channel automatically

All metric collection runs in your CI environment. Dev Herald receives only the structured signals you send. See Data & Privacy for details.

What you can track

Signal	What it measures
`dependencies`	Package counts and vulnerability summary
`bundle`	JS/CSS bundle sizes with per-route breakdown
`unusedCode`	Unused files, dependencies, and type exports
`cve`	Detailed CVE findings from your lockfile

See Signals for what each signal means, Initiatives for long-running counts such as affected files and remaining occurrences, or the API Reference for request schemas.

Where reports appear

Dev Herald dashboard — View the latest report with deltas against the previous snapshot
Slack — Automated summaries delivered to subscribed channels after each CI run

Use cases

Weekly Slack Report — Keep your team informed with automated channel summaries
Security Report — Track CVEs and dependency vulnerabilities over time
Cleanup with Cursor — Turn unused code findings into actionable cleanup work

Getting started

Follow the Quick Start guide to add health reporting to your CI pipeline.