Quality reports
The reports below are produced by CI on every push to main (see .github/workflows/deploy-pages.yml and ADR 0011) and published alongside this documentation site. They are not available in local dev (npm run docs:dev/docs:build) — the links only resolve once deployed to GitHub Pages, since each report is generated by its own tool and merged into the site at deploy time, not built by VitePress itself.
| Report | What it shows | Generated by |
|---|---|---|
| Code coverage | Istanbul/nyc HTML coverage report for the e2e test run | npm run test:e2e:coverage — see Build toolchain → Code coverage |
| Allure report | Step-by-step e2e test results, trend graphs across deployments, categorized failures | npm run test:e2e:allure:generate — see Build toolchain → Allure report |
| Playwright report | Playwright's own interactive test report, with traces/screenshots per test | Playwright's built-in html reporter — see Build toolchain → Test reports |
| SBOM report (prod) | Dependency/license overview (CycloneDX) for runtime dependencies only - what's actually shipped | npm run sbom:report:prod — see Build toolchain → Software Bill of Materials |
| SBOM report (dev) | Same, but for the full dependency tree including devDependencies (build/test tooling) | npm run sbom:report:dev — see Build toolchain → Software Bill of Materials |
The app itself
A build of the app is also published, under /app/ — loaded against the bundled sample PAM.json, since (per ADR 0006) real PAM data is never bundled or published. Use the "Upload PAM.json" button to try it with your own data; nothing you upload leaves your browser (see ADR 0001).
See ADR 0011 for why the site is laid out this way (VitePress at the root, the app and reports under subpaths) and how the Allure trend history survives across deployments.