Problem
Clean origin/main currently fails the repo-wide npm run check gate at the final npm audit --audit-level=moderate step.
The functional gates before audit pass, but audit reports 3 high-severity advisories:
brace-expansion <=1.1.16
fast-uri 3.0.0 - 3.1.3
sharp <0.35.0
This is now blocking unrelated PRs such as #179 even when eval/docs/tests pass.
Evidence
Verified on a detached clean worktree from origin/main (075f1e0):
npm audit --audit-level=moderate
Result: same 3 high-severity advisories.
Verified again on PR #179: remote eval check passes eval, docs, index hygiene, agentic pytest, and python compileall, then fails only at npm audit with the same advisories.
Scope
- Run
npm audit fix and inspect resulting lockfile changes.
- Evaluate whether
[email protected] is safe despite npm marking it as a breaking update.
- Run image/build/eval checks after dependency changes.
- Keep this as a focused dependency/security PR; do not mix with SEO/content changes.
Acceptance criteria
Guardrails
No production deploy, DNS, credential, or public posting changes. Stop at PR boundary unless Kris explicitly approves merge.
Problem
Clean
origin/maincurrently fails the repo-widenpm run checkgate at the finalnpm audit --audit-level=moderatestep.The functional gates before audit pass, but audit reports 3 high-severity advisories:
brace-expansion <=1.1.16fast-uri 3.0.0 - 3.1.3sharp <0.35.0This is now blocking unrelated PRs such as #179 even when eval/docs/tests pass.
Evidence
Verified on a detached clean worktree from
origin/main(075f1e0):Result: same 3 high-severity advisories.
Verified again on PR #179: remote
evalcheck passes eval, docs, index hygiene, agentic pytest, and python compileall, then fails only at npm audit with the same advisories.Scope
npm audit fixand inspect resulting lockfile changes.[email protected]is safe despite npm marking it as a breaking update.Acceptance criteria
npm audit --audit-level=moderatepasses or remaining advisory is documented with a justified exception.npm run checkpasses on a clean worktree.sharpupdate is verified against image-related scripts that depend on it.Guardrails
No production deploy, DNS, credential, or public posting changes. Stop at PR boundary unless Kris explicitly approves merge.