Skip to content

Security: upgrade vitest to 5.1.0 (clears critical npm audit) - #7

Open
buttercode101 wants to merge 2 commits into
mainfrom
fix/vitest-security-upgrade
Open

buttercode101 wants to merge 2 commits into
mainfrom
fix/vitest-security-upgrade

Conversation

@buttercode101

Copy link
Copy Markdown
Owner

Clears 2 critical (tinypool prototype-pollution RCE), 1 high and 2 moderate advisories in the dev-only vitest/vite chain. Production dependencies were already clean (npm audit --omit=dev = 0); this removes RCE-grade advisories from test tooling.\n\nEvidence: npm audit = 0 vulnerabilities; npm test green (node --test 75/75 + vitest 3/3). No application code changed.

…d dev-server)

npm audit reported 2 critical (tinypool prototype-pollution RCE)
+ 1 high + 2 moderate, all in the dev-only vitest/vite chain
(prod audit --omit=dev was already clean; shipped app unaffected,
but test tooling should not carry RCE-grade advisories).

vitest 5.1.0 via npm audit fix --force; full suite green
(node --test 75/75 + vitest UI 3/3). No app code changed.
@vercel

vercel Bot commented Nov 8, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
invoiceflow-za Ready Ready Preview Nov 8, 2026 12:37pm UTC

The README carried a static coverage-100% badge but no CI step
measures coverage (portfolio review 2026-11-06 flagged the same
issue in an earlier index). Removed rather than left misleading.

SECURITY.md was the 500-byte generic template. Replaced with a
product-specific policy: local-first IndexedDB data boundary,
backup-file handling, web-app threat notes, known limitations,
and reporting process. Verified claims only.
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