Share an npm audit report

npm audit is one of the few security tools every JavaScript team already runs, and one of the least acted upon. The output is terminal text, it scrolls past in CI, and its recommendation is frequently npm audit fix --force, which nobody is going to run on a Friday. So the audit becomes noise that the build prints and the team filters out.

The fix is not a different scanner. It is putting the results somewhere a human decision can attach to them.

Have an audit.json already? Drop it into the free npm audit viewer — it turns npm, pnpm or yarn audit JSON into a report with each advisory, its CVSS score, the packages it reaches and the fix, in your browser, and copies a Markdown table for the PR.

Publish it

npm audit --json > audit.json || true
npx npm-audit-html --input audit.json --output audit.html

curl -fsS -X PATCH \
  "https://commareports.com/api/v1/reports/$COMMA_REPORT_ID" \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html audit.html \
        --arg title "npm audit — web — $(date +%F)" \
        '{title: $title, html: $html}')"

|| true because a non-zero exit means findings, which is the case you care about. PATCH keeps one URL per workspace with a revision per run.

Free · no card

Turn your report into a link

Drop an HTML file or paste it. Teammates open one URL and comment on the exact chart or line.

Your file is read in this tab and nothing is uploaded until you publish. Creating an account is free, and reading a shared link never needs one.

Or render your own digest

The full advisory list is not what a team discusses. What it discusses is: what is new since last week, what is high severity and reachable, what is blocked on a major bump. Three rows of HTML built from audit.json beats 900 lines of rendered advisories, and it gives reviewers something short enough to actually read — and to comment on. See commenting on HTML.

What the URL changes

  • Accepted advisories stay accepted, with the reason attached.
  • Each run is a revision, so "did that upgrade help" is a diff, not a memory test.
  • A weekly digest posts itself. A routine can run the audit on a cron and publish the refreshed report to the same URL.

Limits

  • HTML body: 5 MB. Deep dependency trees can render large — publish a digest and attach the raw JSON as an asset.
  • Scripts run, sandboxed: allow-scripts, no allow-same-origin.
  • 60 requests/minute per token. Use a scoped token with reports:write only.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish an audit →

Related

Have an HTML report to share? Publish it free and send one link people can comment on.