chore(deps-dev): bump vite from 5.0.12 to 5.0.13 in /web

[dependabot]

Bumps vite from 5.0.12 to 5.0.13.

Changelog

Sourced from vite's changelog.

5.0.13 (2024-03-24)

• fix: fs.deny with globs with directories (#16250) (d2db33f), closes #16250

Commits

• 80b1b07 release: v5.0.13
• d2db33f fix: fs.deny with globs with directories (#16250)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dryrunsecurity]

DryRun Security Summary

The provided code change is an update to the package.json file in the web directory, where the vite dependency has been updated from version 5.0.12 to 5.0.13, which does not appear to introduce any significant security concerns, but it's important to review the changelog and release notes to ensure that there are no breaking changes or new security vulnerabilities introduced.

Expand for full summary

Summary:

The provided code change is an update to the package.json file in the web directory of the project, where the vite dependency has been updated from version 5.0.12 to 5.0.13. From an application security perspective, this change does not seem to introduce any significant security concerns. Updating dependencies to their latest versions is generally a good practice as it can address known vulnerabilities and improve overall security. However, it's always important to thoroughly review the changelog and release notes of the updated dependency to ensure that there are no breaking changes or new security vulnerabilities introduced.

Additionally, the package.json file contains a large number of dependencies, some of which may have security implications. It's recommended to regularly review all the dependencies in the project and ensure that they are up-to-date and secure. Tools like npm audit or yarn audit can be used to scan the project's dependencies for known vulnerabilities. Overall, this code change appears to be a routine update to a dependency and does not raise any immediate security concerns. However, it's essential to maintain a proactive approach to application security by continuously monitoring dependencies, applying security best practices, and staying vigilant for any potential issues.

Files Changed:

• web/package.json: This file has been updated to include a new version of the vite dependency, changing from 5.0.12 to 5.0.13. This update does not appear to introduce any significant security concerns, but it's important to review the changelog and release notes to ensure that there are no breaking changes or new security vulnerabilities introduced.

Code Analysis

We ran 9 analyzers against 2 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.