-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vulnerabilities Right after a Fresh Setup #19455
Labels
Comments
I'm stupid I didn't read it thoroughly. Apologies. |
@Clotho-ex what did you do to fix this? fix --force ? |
I don't think there's a way to fix it currently. The force fix will break everything |
What's the solution to this? Are we chalking this up as "no fix"? I ran in
|
The answer is here: #19412 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 Vulnerabilities After Fresh Setup
After running the
npm create vite@latest
command and thennpm install
, I'm having 3 moderate severity vulnerabilities. Moreover, when I runnpm install tailwindcss @tailwindcss/vite
, the vulnerability count goes to 4. A week ago when I started a project, I didn't have any issue. I saw another Issue about this but that person did not give extensive information.Reproduction
https://github.com/Clotho-ex/note-taking-app.git
Steps to reproduce
npm create vite@latest
npm install
System Info
#
Used Package Manager
npm
Logs
$ npm audit
npm audit report
esbuild <=0.24.2
Severity: moderate
esbuild enables any website to send any requests to the development server and read the response - GHSA-67mh-4wv8-2f99
fix available via
npm audit fix --force
Will install [email protected], which is a breaking change
node_modules/esbuild
vite >=0.11.0
Depends on vulnerable versions of esbuild
node_modules/vite
@vitejs/plugin-react >=2.0.0-alpha.0
Depends on vulnerable versions of vite
node_modules/@vitejs/plugin-react
3 moderate severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Validations
The text was updated successfully, but these errors were encountered: