Skip to content

[Snyk] Security upgrade vite from 6.2.6 to 6.2.7#127

Closed
mmsge wants to merge 1 commit intomainfrom
snyk-fix-f08775ed6ac7bba08731521affd7a611
Closed

[Snyk] Security upgrade vite from 6.2.6 to 6.2.7#127
mmsge wants to merge 1 commit intomainfrom
snyk-fix-f08775ed6ac7bba08731521affd7a611

Conversation

@mmsge
Copy link
Contributor

@mmsge mmsge commented May 3, 2025

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • www/package.json
  • www/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Directory Traversal
SNYK-JS-VITE-9919777
  174  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Directory Traversal

@mmsge
Copy link
Contributor Author

mmsge commented May 3, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

code/snyk check is complete. No issues have been found. (View Details)

@eoye
Copy link
Contributor

eoye commented May 22, 2025

Done in #129

@eoye eoye closed this May 22, 2025
@eoye eoye deleted the snyk-fix-f08775ed6ac7bba08731521affd7a611 branch May 22, 2025 11:56
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.

3 participants