
The critical that no gate blocked: 39 vulnerabilities and a green deploy
The audit step claimed it blocked the build on known CVEs. It carried continue-on-error from day one. When pnpm audit found a CVSS 9.8 RCE in Astro, the deploy sailed through.
5 posts

The audit step claimed it blocked the build on known CVEs. It carried continue-on-error from day one. When pnpm audit found a CVSS 9.8 RCE in Astro, the deploy sailed through.

Pinning an action version protects nothing: the v4 tag is a moving pointer the repository owner can rewrite. Only the commit SHA is immutable.

Nine libraries, a test runner major bump and a GitHub action updated in a single day. What it took to merge 11 dependabot pull requests on the Portfolio without breaking the suite — and the one that almost turned into a false alarm.

The alarm hunts, the gate blocks, the dog attacks. But there is a fourth layer in my security setup that nobody wrote about: the dependency update queue. On August 31st, the bot delivered five fix proposals. Three days later, all five are still open. The queue became the surface.

pnpm audit on the Portfólio screamed 61 vulnerabilities. Instead of updating dependency by dependency or trusting audit fix, I solved it with 5 lines of pnpm.overrides in package.json. Result: 61 → 2, with the remaining 2 having no published fix at all.