fix(ValidationKit/typescript/guardis): bump vitest ^1.0.0 to ^4.1.0 for CVE-2026-47429

[KooshaPari]

User description

Summary

Resolves Dependabot alert #20 (critical, CVSS 9.8).

CVE

• CVE-2026-47429 / GHSA-5xrq-8626-4rwp
• 'When Vitest UI server is listening, arbitrary file can be read and executed'
• CWE-862: Missing Authorization
• Affected: vitest < 4.1.0
• Patched: vitest >= 4.1.0

Change

Single-version bump in ValidationKit/typescript/guardis/package.json:

-    "vitest": "^1.0.0"
+    "vitest": "^4.1.0"

Why we still care even though UI is not exposed

The Vitest UI server is not exposed to the network in this repo (we only use vitest programmatically via the test script). However, the upstream patch closes the authorization-bypass class entirely and reduces the alert noise on default-branch security advisories.

Lockfile

pnpm-lock.yaml will be regenerated by Dependabot on the resulting PR (after merge).

Test plan

• Local install with pnpm@10.29.3 succeeds
• Lockfile diff is minimal (only vitest 1.x → 4.x line)
• CI workflow will run via Dependabot

Related

• Dismissed (tolerable_risk, no_fix_available): Item: helios-cli 19 #21 (pyo3), Item: helios-cli 38 #34 (fast-uri) — both have no patched versions published yet.

---

CodeAnt-AI Description

Update Vitest to a patched version to close a security issue in the test setup

What Changed

• Upgraded Vitest from 1.x to 4.1.0 in the TypeScript guard package
• This removes exposure to a known security flaw in older Vitest versions

Impact

✅ Safer test runs
✅ Fewer security alerts
✅ Lower risk from outdated test tooling

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[gemini-code-assist]

Code Review

This pull request updates the vitest devDependency in ValidationKit/typescript/guardis/package.json from version ^1.0.0 to ^4.1.0. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​vitest@​4.1.10

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/vitest@4.1.10 → npm/@emnapi/runtime@1.11.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 file)

• ValidationKit/typescript/guardis/package.json

---

_{Reviewed by step-3.7-flash · Input: 108.6K · Output: 9.6K · Cached: 619.9K}