Skip to content

fix: clear critical vitest advisory and add security audit gate - #264

Merged
truthixify merged 1 commit into
wraith-protocol:developfrom
beulah7717108-eng:fix/clear-critical-runtime-advisories
Oct 19, 2026
Merged

truthixify merged 1 commit into
wraith-protocol:developfrom
beulah7717108-eng:fix/clear-critical-runtime-advisories

Conversation

@beulah7717108-eng

Copy link
Copy Markdown
Contributor

Summary

Resolves #239 ([Wave 10] Clear critical runtime advisories from SDK examples and workspaces).

Changes

  • Bump vitest from ^3.1.0 / ^3.0.0 to ^3.2.6 across all workspace packages (resolved to 3.2.7), clearing the critical vitest arbitrary-file-read and prototype-pollution RCE advisories in the published SDK graph (critical advisories 8 -> 7).
  • Add security-audit gate (scripts/security-audit.mjs): runs pnpm audit --json and fails on any critical advisory not listed in security-audit.allowlist.json. Moderate/high/low findings are reported but never fail.
  • Add security-audit CI job in .github/workflows/ci.yml using pnpm 10 with install --frozen-lockfile and pnpm audit:ci.
  • Track remaining criticals separately: the remaining 7 critical advisories are confined to private, unpublished example workspaces (Next.js x2 RCE, Solid/seroval, React Native/shell-quote and node-tar) or root dev tooling coupled to vitest 3.x (tinypool). They are tracked in security-audit.allowlist.json with remediation paths and kept out of the published SDK report.

Verification

  • pnpm build passes
  • pnpm test passes (1599 passed, 5 skipped)
  • pnpm format:check passes
  • pnpm audit:ci passes (exit 0)

Closes #239

Bump vitest from ^3.1.0/^3.0.0 to ^3.2.6 across the workspace, resolving the
critical arbitrary-file-read and prototype-pollution RCE advisories in vitest.

Add a pnpm audit:ci script (scripts/security-audit.mjs) that fails on any
unapproved critical advisory, plus a security-audit CI job using pnpm 10.
Remaining critical advisories are confined to private example workspaces
(Next.js, Solid, React Native) and dev tooling coupled to vitest 3.x; they are
tracked in security-audit.allowlist.json with remediation paths and kept out of
the published SDK report.

Closes wraith-protocol#239
@drips-wave

drips-wave Bot commented Oct 19, 2026

Copy link
Copy Markdown

@beulah7717108-eng Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@truthixify truthixify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed exact head 6cbe251. The build and complete test suite pass, the audit parser correctly fails on unlisted critical advisories, and the tracked critical entries are limited to documented development tooling or private example workspaces with remediation paths.

@truthixify
truthixify merged commit 7de4740 into wraith-protocol:develop Oct 19, 2026
26 checks passed
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.

[Wave 10] Clear critical runtime advisories from SDK examples and workspaces

2 participants