fix(test): boot API tests on a throwaway DB + 41 new tests + auto badges

The CI failure (`POST /api/achievements/recompute` -> expected 0 to be
greater than 0) was an environment leak: the API tests started the server
against the REAL data/tracker.db and ~/.claude. On a dev machine that
happened to pass; in CI, with neither, the aggregator was empty. It also
made the suite take 33s and let the recompute test rewrite the developer's
own achievements table.

DATA_DIR/DB_PATH are env-overridable now. The API tests boot on a temp DB
with an empty CLAUDE_DIR and seed a deterministic 45-day history
(test/fixtures/history.js). Suite: 33s -> 0.6s, and reproducible.

41 new tests (255 -> 296), all asserting behaviour rather than shapes:
- parser: rate-limit events + stable ids, /subagents/ detection, line
  counting from Edit/Write input, incremental offsets
- db: device CRUD & key regeneration, device deletion orphans messages,
  duplicate rate-limit events, project shares incl. expiry
- aggregator: previous-month clamping (Mar 31 -> Feb 28), Monday week
  start, future-dated messages, empty payload, momentum filtering,
  90 gapless local days
- achievements: backfill determinism, atomic replace preference, no-op on
  empty history, tier-scaled sample gates (4d/10d/31d boundaries)
- api: real numbers against the seeded history, MCP typing/grouping,
  sub-agent share, public pricing endpoint, 404 for unknown routes
- config: DATA_DIR/DB_PATH resolution

Badges: test count and LOC are generated by scripts/update-badges.js from
the vitest JSON report and git ls-files, shown prominently at the top of
all three READMEs, and refreshed on every push to main by
.github/workflows/badges.yml. The hand-maintained numbers had drifted
(badge said 238 tests, suite had 255; "LOC 25k+" was a guess).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: pepperonas

.github/workflows/badges.yml

@@ -0,0 +1,43 @@
+name: Badges
+
+# Keeps the test-count and lines-of-code badges in the READMEs honest: they are
+# recomputed from the actual suite + tracked sources on every push to main and
+# committed back. Hand-maintained numbers always drifted (the badge claimed 238
+# tests while the suite had 255).
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: write
+
+concurrency:
+  group: badges-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  update:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+      - run: npm ci
+      - name: Run the suite with a JSON report
+        run: npx vitest run --reporter=json --outputFile=.vitest-report.json
+      - name: Recompute badges
+        run: node scripts/update-badges.js --report .vitest-report.json
+      - name: Commit if the numbers moved
+        run: |
+          rm -f .vitest-report.json
+          if [ -z "$(git status --porcelain README.md README_EN.md README_DE.md)" ]; then
+            echo "Badges already up to date."
+            exit 0
+          fi
+          git config user.name 'github-actions[bot]'
+          git config user.email '41898282+github-actions[bot]@users.noreply.github.com'
+          git add README.md README_EN.md README_DE.md
+          git commit -m 'chore: refresh test/LOC badges [skip ci]'
+          git push

.gitignore

@@ -18,3 +18,6 @@ sync-agent/node_modules/
 # Runtime logs (LaunchAgent/PM2)
 stdout.log
 stderr.log
+
+# Vitest JSON report (badge automation)
+.vitest-report.json

CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog
 
+## [Unreleased] - 2026-07-22 (Tests & Badges)
+
+### Fixed
+- **CI-Fehlschlag `POST /api/achievements/recompute` (`expected 0 to be greater than 0`)** — die API-Tests starteten den Server gegen die **echte** `data/tracker.db` und das echte `~/.claude`. Lokal lief das (zufällig) durch, in CI gibt es beides nicht → 0 Nachrichten → 0 Achievements. Nebenwirkungen: die Suite brauchte ~33 s und der Recompute-Test **überschrieb die reale Achievements-Tabelle des Entwicklers**. `DATA_DIR`/`DB_PATH` sind jetzt per Env überschreibbar; die API-Tests booten gegen eine Wegwerf-DB in `mkdtemp()` mit leerem `CLAUDE_DIR` und seeden vorher eine deterministische 45-Tage-History (`test/fixtures/history.js`). **Suite: 33 s → 0,6 s**, und sie ist reproduzierbar statt vom Rechner abhängig
+
+### Added
+- **41 neue Tests (255 → 296)**, überall dort, wo bisher nur die Response-*Form* geprüft wurde:
+  - **Parser**: Rate-Limit-Events (inkl. stabiler, aus Session+Timestamp abgeleiteter ID → Re-Parse dupliziert nicht), Sub-Agent-Erkennung über den `/subagents/`-Pfad, Zeilenzählung aus `Edit`/`Write`-Tool-Input, Offset-Fortschreibung beim inkrementellen Parsen
+  - **DB**: Geräte-CRUD (eindeutige API-Keys, Key-Regenerierung invalidiert den alten Key, Löschen eines Geräts **verwaist** die Nachrichten statt sie zu löschen), Rate-Limit-Events (Duplikate werden ignoriert, leerer Batch), Projekt-Shares (48-stelliges Token, abgelaufene Shares sind öffentlich unsichtbar, bleiben aber verwaltbar, Löschen)
+  - **Aggregator**: Vormonats-Cutoff-Clamping (31.03. → 28.02.), Montag als Wochenstart (Sonntag zählt zur abgelaufenen Woche), Zukunftsdaten werden ignoriert, leerer Aggregator liefert ein Null-Payload, Momentum-Einträge ohne Volumen fallen raus, `daily90` sind 90 lückenlose aufeinanderfolgende Lokaltage
+  - **Achievements**: Backfill ist deterministisch (zwei Läufe = identische Daten), nutzt die atomare `replaceAchievementsForUser`-API wenn vorhanden, macht bei leerer History nichts (löscht insbesondere nichts) und die **Sample-Gates greifen stufenweise** (4 aktive Tage: kein Gold; 10: Gold, aber kein Platin/Diamant; 31: alle)
+  - **API**: echte Zahlen statt Formen — Overview zählt die geseedeten 270 Nachrichten/90 Sessions/45 aktiven Tage, `/api/daily` deckt alle 45 Tage ab und summiert sich zum Overview, `daily90` endet auf heute, Heatmap-Summe == Overview, Tool-Kosten-Attribution inkl. MCP-Typisierung, MCP-Server-Gruppierung, Sub-Agent-Anteil, öffentliches `/api/pricing`, Zeitraumfilter verengt das Ergebnis, unbekannte `/api/*`-Routen liefern 404
+  - **Config**: `DATA_DIR`/`DB_PATH`-Auflösung inkl. relativer Pfade
+- **Automatisch aktualisierte Badges** ganz oben in allen drei READMEs: **Tests** (aus dem echten Vitest-JSON-Report, nicht geschätzt) und **Lines of Code** (aus `git ls-files` über `*.js`/`*.css`/`*.html`). `scripts/update-badges.js` schreibt den Block zwischen `<!-- BADGES:START/END -->`, `npm run badges` lokal, und der neue Workflow `.github/workflows/badges.yml` rechnet sie bei **jedem Push auf main** neu und committet sie zurück (`[skip ci]`). Die handgepflegten Zahlen waren chronisch veraltet (Badge: 238 Tests, Suite: 255; „LOC 25k+" geraten statt gemessen)
+
 ## [Unreleased] - 2026-07-22
 
 ### Added

CLAUDE.md

@@ -11,6 +11,7 @@ npm run test:watch       # Tests in watch mode
 npm run test:coverage    # Coverage report
 npm run lint             # ESLint (lib/ + server.js only)
 npx vitest run test/parser.test.js  # Run a single test file
+npm run badges           # Recompute the test/LOC badges in all READMEs
 bash scripts/deploy.sh   # Deploy to VPS (tracker.celox.io)
 ```
 
@@ -168,5 +169,6 @@ VPS deployment to tracker.celox.io:
 - **Costs**: Rounded to 2 decimals
 - **Unused variables**: Prefix with `_` (ESLint configured for this)
 - **German text**: Use proper umlauts (ü, ö, ä, ß), never ASCII substitutes (ue, oe, ae, ss)
-- **Tests**: Use vitest globals (no imports needed), temp dirs via `fs.mkdtempSync()`, API tests spawn server on random port. Multi-user tests set `MULTI_USER=true` in env and clear require cache. Modules whose config is read at require time (`config.js`, and anything reading `SESSION_SECRET`/`MULTI_USER` such as `anthropic-api.js`) are tested by setting `process.env` **before** a fresh `require`, with `delete require.cache[require.resolve(...)]` and env restored in `afterEach`. Coverage by file: `parser`, `aggregator` (+ `aggregator-cache`), `db`, `auth`, `pricing` (+ `pricing-fetcher`), `achievements`, `backup`, `sync`, `api`, `multi-user-api`, plus `export-html` (pure HTML/escaping/optional-tab rendering), `anthropic-api` (AES-256-GCM `encryptKey`/`decryptKey` round-trip + auth-tag tamper detection + admin-key storage/env-fallback resolution), and `config` (env defaults/overrides, `BASE_URL` and `CLAUDE_DIR`/`PROJECTS_DIR` derivation).
+- **Tests**: Use vitest globals (no imports needed), temp dirs via `fs.mkdtempSync()`. **Nothing may touch the real environment**: the API tests boot the server against a throwaway DB by setting `DB_PATH` + `CLAUDE_DIR` (both env-resolved in `config.js`) **before** requiring `lib/config`/`lib/db`/`lib/aggregator`/`server`, and seed it via `test/fixtures/history.js` (`buildHistory({days, perDay})` — a deterministic, index-derived multi-day history across 3 projects / 3 models / MCP + sub-agent messages). They previously booted on `data/tracker.db` and `~/.claude`, which made the suite 33 s long, machine-dependent (CI, with no data, failed on the achievements test) and let `POST /api/achievements/recompute` rewrite the developer's real achievements. Multi-user tests set `MULTI_USER=true` in env and clear the require cache. Modules whose config is read at require time (`config.js`, and anything reading `SESSION_SECRET`/`MULTI_USER` such as `anthropic-api.js`) are tested by setting `process.env` **before** a fresh `require`, with `delete require.cache[require.resolve(...)]` and env restored in `afterEach`. Prefer asserting **numbers over shapes** — `expect(body.messages).toBe(45 * 6)` catches an aggregation regression, `expect(Array.isArray(body))` does not. Coverage by file: `parser` (incl. rate-limit events, sub-agent path detection, line counting, offsets), `aggregator` (+ `aggregator-cache`, incl. calendar edge cases: previous-month clamping, Monday week start, future-dated messages, empty payloads), `db` (incl. devices, rate-limit events, project shares), `auth`, `pricing` (+ `pricing-fetcher`), `achievements` (incl. backfill determinism, atomic replace, tier-scaled sample gates), `backup`, `sync`, `api`, `multi-user-api`, plus `export-html` (pure HTML/escaping/optional-tab rendering), `anthropic-api` (AES-256-GCM `encryptKey`/`decryptKey` round-trip + auth-tag tamper detection + admin-key storage/env-fallback resolution), and `config` (env defaults/overrides, `BASE_URL`, `CLAUDE_DIR`/`PROJECTS_DIR` and `DATA_DIR`/`DB_PATH` derivation).
+- **README badges**: the test-count and LOC badges at the top of `README.md`/`README_EN.md`/`README_DE.md` are **generated**, never hand-edited — `scripts/update-badges.js` rewrites the block between `<!-- BADGES:START -->` / `<!-- BADGES:END -->` from the real vitest JSON report and `git ls-files`. `.github/workflows/badges.yml` runs it on every push to `main` and commits the result (`[skip ci]`); `npm run badges` does the same locally. Editing the numbers by hand just gets overwritten on the next push.
 - **ESLint**: Flat config (ESLint 9), only covers `lib/` and `server.js`

README.md

@@ -8,6 +8,13 @@
   Real-time dashboard for Claude Code token usage, API-equivalent cost estimation, and coding activity tracking.
 </p>
 
+<!-- BADGES:START -->
+<p align="center">
+  <img src="https://img.shields.io/badge/tests-296_passing-3fb950?style=for-the-badge&logo=vitest&logoColor=white" alt="296 tests passing">
+  <img src="https://img.shields.io/badge/code-31.8k_lines-58a6ff?style=for-the-badge&logo=javascript&logoColor=white" alt="31775 lines of code across 45 files">
+</p>
+<!-- BADGES:END -->
+
 <p align="center">
   <a href="https://github.com/pepperonas/claude-token-tracker/actions/workflows/ci.yml"><img src="https://github.com/pepperonas/claude-token-tracker/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
   <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="License: MIT"></a>
@@ -20,7 +27,6 @@
   <img src="https://img.shields.io/badge/Node.js-%3E%3D20.12-339933?logo=node.js&logoColor=white" alt="Node.js >= 20.12">
   <img src="https://img.shields.io/badge/SQLite-WAL_Mode-003B57?logo=sqlite&logoColor=white" alt="SQLite WAL">
   <img src="https://img.shields.io/badge/Chart.js-4.x-FF6384?logo=chartdotjs&logoColor=white" alt="Chart.js">
-  <img src="https://img.shields.io/badge/Vitest-255_tests-6E9F18?logo=vitest&logoColor=white" alt="Tests">
   <img src="https://img.shields.io/badge/ESLint-9.x-4B32C3?logo=eslint&logoColor=white" alt="ESLint">
 </p>
 
@@ -37,7 +43,6 @@
   <img src="https://img.shields.io/badge/deps-2_runtime-success" alt="Dependencies">
   <img src="https://img.shields.io/badge/no_framework-vanilla_JS-yellow" alt="No Framework">
   <img src="https://img.shields.io/badge/API-50+_endpoints-blue" alt="API Endpoints">
-  <img src="https://img.shields.io/badge/LOC-25k+-informational" alt="Lines of Code">
 </p>
 
 <p align="center">
@@ -152,7 +157,7 @@ Open [http://localhost:5010](http://localhost:5010)
 - **Token breakdown** — Input, Output, Cache Read, Cache Create with per-type API-equivalent cost estimation
 - **Share API** — secure external API for sharing project-specific token usage data with clients. Share tokens (48-char hex, 192-bit entropy) expose sanitized project data (tokens, cost, sessions, code lines, daily breakdown) via public endpoints. Admin key authentication for share management, rate limiting (30 req/min/IP), CORS restrictions, and optional expiry. Used by [OPS](https://github.com/pepperonas/celox-ops) for customer transparency dashboards. Settings UI shows Share Admin Key with copy button.
 - **Database download** — download the full SQLite database from Settings for local backup or analysis
-- **255 automated tests** — unit, integration, and multi-user API tests
+- **296 automated tests** — unit, integration, and multi-user API tests
 - **Zero-framework frontend** — vanilla JS, 2 runtime dependencies, no build step
 
 ## Screenshots

README_DE.md

@@ -2,6 +2,13 @@
   <a href="README_EN.md"><img src="https://img.shields.io/badge/%F0%9F%87%AC%F0%9F%87%A7_English-Switch_Language-blue?style=for-the-badge" alt="Switch to English"></a>
 </p>
 
+<!-- BADGES:START -->
+<p align="center">
+  <img src="https://img.shields.io/badge/tests-296_passing-3fb950?style=for-the-badge&logo=vitest&logoColor=white" alt="296 tests passing">
+  <img src="https://img.shields.io/badge/code-31.8k_lines-58a6ff?style=for-the-badge&logo=javascript&logoColor=white" alt="31775 lines of code across 45 files">
+</p>
+<!-- BADGES:END -->
+
 <p align="center">
   <a href="https://github.com/pepperonas/claude-token-tracker/actions/workflows/ci.yml"><img src="https://github.com/pepperonas/claude-token-tracker/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
   <a href="LICENSE"><img src="https://img.shields.io/badge/Lizenz-MIT-blue.svg" alt="Lizenz: MIT"></a>
@@ -14,7 +21,6 @@
   <img src="https://img.shields.io/badge/Node.js-%3E%3D20.12-339933?logo=node.js&logoColor=white" alt="Node.js >= 20.12">
   <img src="https://img.shields.io/badge/SQLite-WAL--Modus-003B57?logo=sqlite&logoColor=white" alt="SQLite WAL">
   <img src="https://img.shields.io/badge/Chart.js-4.x-FF6384?logo=chartdotjs&logoColor=white" alt="Chart.js">
-  <img src="https://img.shields.io/badge/Vitest-255_Tests-6E9F18?logo=vitest&logoColor=white" alt="Tests">
   <img src="https://img.shields.io/badge/ESLint-9.x-4B32C3?logo=eslint&logoColor=white" alt="ESLint">
 </p>
 
@@ -31,7 +37,6 @@
   <img src="https://img.shields.io/badge/Deps-2_Runtime-success" alt="Abhängigkeiten">
   <img src="https://img.shields.io/badge/kein_Framework-Vanilla_JS-yellow" alt="Kein Framework">
   <img src="https://img.shields.io/badge/API-50+_Endpunkte-blue" alt="API Endpunkte">
-  <img src="https://img.shields.io/badge/LOC-25k+-informational" alt="Codezeilen">
 </p>
 
 <p align="center">
@@ -192,7 +197,7 @@ Dashboard zur Analyse deiner Claude Code Token-Nutzung. Liest die JSONL-Sitzungs
 - **Perioden-Vergleich** — immer sichtbare Pill-Leiste (Aus / Vorperiode / Letzte 7T / 30T / 90T / Eigener) vergleicht zwei Zeiträume sofort nebeneinander mit 8 Metriken (Tokens/Min, Zeilen/Stunde, Kosten/Zeile, Tokens/Zeile, Zeilen/Nachricht, Tools/Nachricht, I/O-Verhältnis, Coding-Stunden), Delta-Prozenten und farbcodierten Verbesserungs-/Verschlechterungsanzeigen — ein Klick genügt, kein separater Toggle nötig
 - **HTML-Export** — mobil-optimierter interaktiver Snapshot mit Chart.js, 8 Tabs (Übersicht, Charts, Sitzungen, Projekte, Modelle, Tools, Produktivität, Achievements), 12+ Charts und sortierbaren Tabellen. Optimiert für Smartphones (412px+) mit adaptiven Layouts, Touch-freundlichen Tabs und responsiven Chart-Darstellungen
 - **Globaler Vergleich** — eigene Statistiken gegen den Durchschnitt aller Nutzer vergleichen (Multi-User-Modus)
-- **255 automatisierte Tests** (Unit + Integration + Multi-User API + Achievements)
+- **296 automatisierte Tests** (Unit + Integration + Multi-User API + Achievements)
 
 ## Mobile Screenshots (iPhone 16 — 393px)
 
@@ -457,7 +462,7 @@ Alle GET-Endpunkte unterstützen `?from=YYYY-MM-DD&to=YYYY-MM-DD` Query-Paramete
 ## Entwicklung
 
 ```bash
-npm test              # Alle 255 Tests ausführen (vitest)
+npm test              # Alle 296 Tests ausführen (vitest)
 npm run test:watch    # Tests im Watch-Modus
 npm run test:coverage # Coverage-Report
 npm run lint          # ESLint (lib/ + server.js)

README_EN.md

@@ -2,6 +2,13 @@
   <a href="README_DE.md"><img src="https://img.shields.io/badge/%F0%9F%87%A9%F0%9F%87%AA_Deutsch-Sprache_wechseln-blue?style=for-the-badge" alt="Auf Deutsch wechseln"></a>
 </p>
 
+<!-- BADGES:START -->
+<p align="center">
+  <img src="https://img.shields.io/badge/tests-296_passing-3fb950?style=for-the-badge&logo=vitest&logoColor=white" alt="296 tests passing">
+  <img src="https://img.shields.io/badge/code-31.8k_lines-58a6ff?style=for-the-badge&logo=javascript&logoColor=white" alt="31775 lines of code across 45 files">
+</p>
+<!-- BADGES:END -->
+
 <p align="center">
   <a href="https://github.com/pepperonas/claude-token-tracker/actions/workflows/ci.yml"><img src="https://github.com/pepperonas/claude-token-tracker/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
   <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="License: MIT"></a>
@@ -14,7 +21,6 @@
   <img src="https://img.shields.io/badge/Node.js-%3E%3D20.12-339933?logo=node.js&logoColor=white" alt="Node.js >= 20.12">
   <img src="https://img.shields.io/badge/SQLite-WAL_Mode-003B57?logo=sqlite&logoColor=white" alt="SQLite WAL">
   <img src="https://img.shields.io/badge/Chart.js-4.x-FF6384?logo=chartdotjs&logoColor=white" alt="Chart.js">
-  <img src="https://img.shields.io/badge/Vitest-255_tests-6E9F18?logo=vitest&logoColor=white" alt="Tests">
   <img src="https://img.shields.io/badge/ESLint-9.x-4B32C3?logo=eslint&logoColor=white" alt="ESLint">
 </p>
 
@@ -31,7 +37,6 @@
   <img src="https://img.shields.io/badge/deps-2_runtime-success" alt="Dependencies">
   <img src="https://img.shields.io/badge/no_framework-vanilla_JS-yellow" alt="No Framework">
   <img src="https://img.shields.io/badge/API-50+_endpoints-blue" alt="API Endpoints">
-  <img src="https://img.shields.io/badge/LOC-25k+-informational" alt="Lines of Code">
 </p>
 
 <p align="center">
@@ -192,7 +197,7 @@ Dashboard for analyzing your Claude Code token usage. Reads Claude Code's JSONL
 - **Period comparison** — always-visible inline pill selector (Off / Prev. Period / Last 7d / 30d / 90d / Custom) instantly compares two periods side-by-side with 8 metrics (Tokens/Min, Lines/Hour, Cost/Line, Tokens/Line, Lines/Turn, Tools/Turn, I/O Ratio, Coding Hours), delta percentages, and color-coded improvement/regression indicators — one click to activate, no toggle needed
 - **HTML export** — mobile-responsive interactive snapshot with Chart.js, 8 tabs (Overview, Charts, Sessions, Projects, Models, Tools, Productivity, Achievements), 12+ charts, and sortable tables. Optimized for phones (412px+) with adaptive layouts, touch-friendly tabs, and responsive chart rendering
 - **Global comparison** — compare your stats against the average of all users (multi-user mode)
-- **255 automated tests** (unit + integration + multi-user API + achievements)
+- **296 automated tests** (unit + integration + multi-user API + achievements)
 
 ## Mobile Screenshots (iPhone 16 — 393px)
 
@@ -457,7 +462,7 @@ All GET endpoints support `?from=YYYY-MM-DD&to=YYYY-MM-DD` query parameters. Ana
 ## Development
 
 ```bash
-npm test              # Run all 255 tests (vitest)
+npm test              # Run all 296 tests (vitest)
 npm run test:watch    # Watch mode
 npm run test:coverage # Coverage report
 npm run lint          # ESLint (lib/ + server.js)

lib/config.js

@@ -7,9 +7,17 @@ const CLAUDE_DIR = process.env.CLAUDE_DIR
   : path.join(HOME, '.claude');
 
 const PROJECTS_DIR = path.join(CLAUDE_DIR, 'projects');
-const DATA_DIR = path.join(__dirname, '..', 'data');
+// DATA_DIR/DB_PATH are env-overridable so tests (and any second instance) can
+// run against a throwaway database instead of the developer's real one — the
+// API tests used to boot the server on `data/tracker.db` and rewrite its
+// achievements table.
+const DATA_DIR = process.env.DATA_DIR
+  ? path.resolve(process.env.DATA_DIR)
+  : path.join(__dirname, '..', 'data');
 const PORT = parseInt(process.env.PORT, 10) || 5010;
-const DB_PATH = path.join(DATA_DIR, 'tracker.db');
+const DB_PATH = process.env.DB_PATH
+  ? path.resolve(process.env.DB_PATH)
+  : path.join(DATA_DIR, 'tracker.db');
 const BACKUP_PATH = process.env.BACKUP_PATH || '';
 const BACKUP_INTERVAL_HOURS = parseInt(process.env.BACKUP_INTERVAL_HOURS, 10) || 6;
 const STATS_CACHE_FILE = path.join(CLAUDE_DIR, 'stats-cache.json');

package.json

@@ -9,6 +9,7 @@
     "test:watch": "vitest",
     "test:coverage": "vitest run --coverage",
     "lint": "eslint lib/ server.js",
+    "badges": "vitest run --reporter=json --outputFile=.vitest-report.json && node scripts/update-badges.js --report .vitest-report.json && rm -f .vitest-report.json",
     "postinstall": "node scripts/setup.js"
   },
   "author": "Martin Pfeffer",