fix: update vite to ^7.1.11 to remediate CVE-2025-62522

[Copilot]

Summary

This PR remediates the medium severity vulnerability CVE-2025-62522 identified in the vite package used by the dashboard component.

Vulnerability Details

• CVE: CVE-2025-62522
• Severity: Medium
• Affected Package: vite
• Vulnerable Versions: >= 7.1.0, <= 7.1.10
• Issue: Server.fs.deny bypass via backslash on Windows
• Patched Versions: 5.4.21, 6.4.1, 7.0.8, 7.1.11+

Changes

Updated the vite dependency in packages/dashboard/package.json from ^7.1.7 to ^7.1.11, which resolved to version 7.1.12 in the lockfile. This version includes the security patch for CVE-2025-62522.

Verification

• ✅ Verified no vulnerabilities exist in vite 7.1.12 using gh-advisory-database
• ✅ Successfully built the dashboard with the updated vite version
• ✅ Confirmed minimal changes (only package.json and yarn.lock modified)

Impact

This is a low-risk dependency update that addresses a security vulnerability without affecting any functionality. The dashboard builds successfully with the new version, maintaining full backward compatibility.

Fixes vulnerability reported in https://github.com/taskforcesh/nandu/security/dependabot/140

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Vanta] Remediate "Medium vulnerabilities identified in packages are addressed (GitHub Repo)" for npm-vite >= 7.1.0, <= 7.1.10/CVE-2025-62522 (nandu)</issue_title>
<issue_description>What's wrong?
You have open medium severity vulnerabilities.

Github Vulnerability

• npm-vite >= 7.1.0, <= 7.1.10/CVE-2025-62522 (nandu)

How to fix?

1. Visit the Vulnerabilities page to learn more about the unresolved vulnerabilities.
2. Remediate or deactivate monitoring for each unresolved vulnerability.
3. Optional] If the vulnerability was resolved outside of the SLA you’ve defined, explain the reason to your auditor on the [SLA violations page.

This issue was automatically created from Vanta. View test in Vanta</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes #41

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.