We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
npm i @nut-tree/[email protected] Then we can see vulnerabilities dependencies. Better to solve it.
npm i @nut-tree/[email protected]
The text was updated successfully, but these errors were encountered:
Hi @QimatLuo 👋
while we're waiting for an upstream fix I published a short advisory how users can mitigate these vulnerabilities in the meantime: https://nutjs.dev/blog/jimp-security-advisory
Sorry, something went wrong.
Works for me. Should I close this issue now? or just wait for the upstream fix then close this issue?
You can keep it open, I'll close it once it's fixed upstream
(#422) Bumped jimp, ts-node, typedoc and typescript to close vulnerab…
2670939
…ilities
6ca94cc
…ilities (#431)
Successfully merging a pull request may close this issue.
npm i @nut-tree/[email protected]
Then we can see vulnerabilities dependencies.
Better to solve it.
The text was updated successfully, but these errors were encountered: