Skip to content

fix(deps): clear 11 HIGH/CRITICAL advisories by raising override floors - #105

Merged
acamarata merged 1 commit into
mainfrom
fix/deps-audit-2026-09-09
Sep 9, 2026
Merged

fix(deps): clear 11 HIGH/CRITICAL advisories by raising override floors#105
acamarata merged 1 commit into
mainfrom
fix/deps-audit-2026-09-09

Conversation

@acamarata

Copy link
Copy Markdown
Contributor

Closes the scheduled audit failure on ce8044ef (run 34343940983), which reported 13 unpatched HIGH/CRITICAL findings.

Every advisory was already covered by an entry in the root pnpm.overrides — the floors had just fallen behind the releases carrying the fixes, so the lockfile stayed pinned below them.

package old floor new floor resolved
@xmldom/xmldom (7 advisories) >=0.8.13 >=0.8.15 0.8.15
js-yaml 4.x ^4.3.0 ^4.3.2 4.3.2
js-yaml 3.x ^3.15.1 ^3.15.2 3.15.2
svgo ^4.0.2 ^4.1.0 4.1.0
sharp ^0.35.0 ^0.35.4 0.35.4
astro (web) ^7.2.4 ^7.2.8 7.3.1

No majors, no upper bounds touched, no allowlist entries added — every advisory here had a real patch. org/ was left alone; its astro ^7.2.10 already satisfied the floor.

Why raise a floor that already resolved correctly. A >=X floor that happens to land on a patched version is protection by coincidence — anything in the tree asking for a lower release is still free to pull one in. The floor is what makes it a guarantee.

Verified locally

  • pnpm install --frozen-lockfile — exit 0, so CI's install step will pass
  • pnpm audit --audit-level=high13 -> 0 violations; the only remaining findings are the two pre-existing allowlisted image-size entries, untouched
  • Each package resolves to exactly one version; no vulnerable copy left alongside a patched one

Why a PR and not a push to main

web/vercel.json and org/vercel.json build every production push, so pushing this to main would production-deploy praycalc.com and praycalc.org. Preview builds are skipped, so this PR costs no build minutes. Merging is the deploy approval — per ASI Policy 9.0 that decision is the owner's.

…ories

The scheduled audit failed with 13 unpatched HIGH/CRITICAL findings. Every
one of them was already covered by an entry in the root pnpm.overrides — the
floors had simply fallen behind the versions that carry the fixes, so the
lockfile stayed pinned below them:

  @xmldom/xmldom  >=0.8.13 -> >=0.8.15   (7 advisories)
  js-yaml 4.x     ^4.3.0   -> ^4.3.2
  js-yaml 3.x     ^3.15.1  -> ^3.15.2
  svgo            ^4.0.2   -> ^4.1.0
  sharp           ^0.35.0  -> ^0.35.4
  astro (web)     ^7.2.4   -> ^7.2.8     (CRITICAL, GHSA-26w7-cxv4-gfx2)

No major upgrades and no upper bounds touched — each floor moves to the
minimum patched release and the lockfile is regenerated to match. org/ was
left alone: its astro ^7.2.10 already satisfied the floor.

A `>=X` floor that happens to resolve to a patched version is protection by
coincidence; anything in the tree asking for a lower release is still free to
pull one in. Raising the floor is what makes it a guarantee.

Verified locally: pnpm install --frozen-lockfile exits 0, and pnpm audit
--audit-level=high now reports only the two pre-existing allowlisted
image-size advisories (13 -> 0 violations). The allowlist was not touched;
every advisory here had a real patch, so none of them needed one.
@vercel

vercel Bot commented Sep 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments
Project Deployment Actions Updated
ummat-praycalc Ignored Ignored Sep 9, 2026 3:54pm UTC
ummat-praycalc-org Ignored Ignored Sep 9, 2026 3:54pm UTC

Request Review

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

🟢 Rampart Security Gate — CLEAN

Tool CRITICAL HIGH MEDIUM LOW
(no findings)

Totals: 0 critical · 0 high · 0 medium · 0 low

Mode: RAMPART_ENFORCE=warn

@acamarata
acamarata merged commit 5abaa2a into main Sep 9, 2026
19 checks passed
@acamarata
acamarata deleted the fix/deps-audit-2026-09-09 branch September 9, 2026 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant