CI setup

Run cms-lab after your app is built and serving. The scanner exits with a stable status code and can produce a single static HTML report artifact.

GitHub Actions

name: cms-lab
on: [pull_request]

jobs:
  scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - uses: actions/setup-node@v6
        with:
          node-version: 22
      - run: corepack enable
      - run: corepack prepare pnpm@10.33.4 --activate
      - run: pnpm install --frozen-lockfile
      - run: pnpm build
      - run: pnpm start &
      - run: pnpm dlx wait-on http://localhost:3000
      - run: npx @cms-lab/cli scan --ci --report
      - uses: actions/upload-artifact@v7
        if: always()
        with:
          name: cms-lab-report
          path: .cms-lab/report.html

Thresholds

By default, errors fail the job and warnings do not. Tighten that after the project has a baseline.

npx @cms-lab/cli scan --ci --fail-on error
npx @cms-lab/cli scan --ci --fail-on warning
npx @cms-lab/cli scan --ci --max-warnings 0
npx @cms-lab/cli scan --ci --max-info 0
npx @cms-lab/cli scan --ci --strict
npx @cms-lab/cli scan --ci --fail-on never

Artifacts

The report is a self-contained HTML file. It can be opened locally, uploaded as a CI artifact, or attached to release notes.