ci: publish pnpm audit findings to a vulnerability dashboard issue #167
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!167
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/vulnerability-dashboard"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Renovate's dependency dashboard covers declared dependencies.
pnpm auditwalks the resolved lockfile tree. Measured on the same commit, 2026-09-23:
Every one of the 41 is 5–10 levels deep and declared nowhere in the repo:
Neither tool is wrong — they answer different questions. Only one of them had a
reporting surface. This adds the other.
What it does
The nightly audit now renders its findings into a single issue,
"Vulnerability Dashboard (pnpm audit)", updated in place each run — the same
shape as Renovate's dashboard. Grouped by package, severity-sorted, with the
advisory link and one dependency path per finding.
It also explains where remediation goes: a
pnpm.overridesentry inpnpm-workspace.yaml, which is what the twelve existing pins already are.Revises the failure semantics from #161
#161 made this job fail on any finding, matching
disk-maintenance.yml's"a scheduled-run failure is the notification".
That was wrong here. With 41 standing advisories the job would have gone red
on its first run tomorrow and stayed red — alert fatigue, not an alert. My
reasoning imported a pattern that fits a binary condition (disk over threshold)
into one with a permanent non-zero baseline.
Now: the issue is the notification. The run fails only when the audit cannot run
or the issue cannot be updated — when the signal is broken, not when it has
something to say.
Verification so far
The renderer was tested against synthetic audit JSON for both the populated and
empty cases. Untested: the live
pnpm audit --jsonoutput shape and whethersecrets.GITHUB_TOKENcan create/update issues on this Forgejo — thecancel-superseded-ci.ymlprecedent shows that token is not permitted tocancel runs, so it may be similarly restricted here. If it is, this needs a PAT,
and the first run will say so.