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
I have identified two vulnerable devDependencies that probably can be bumped to the highest major within the current ^ semver range.
devDependencies
^
https://devhub.checkmarx.com/cve-details/Cxc7705965-e0f0/
https://devhub.checkmarx.com/cve-details/CVE-2022-31051/
Find the highest published version that wouldn't break the current ^ semver and install that version. Useful commands:
Find out:
npm view @babel/core
npm view @babel/core versions
npm view semantic-release
npm view semantic-release versions
Fix:
npm install --save-dev @babel/[email protected]
npm install --save-dev semantic-release@???
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue
I have identified two vulnerable
devDependencies
that probably can be bumped to the highest major within the current^
semver range.@babel/core
https://devhub.checkmarx.com/cve-details/Cxc7705965-e0f0/
semantic-release
https://devhub.checkmarx.com/cve-details/CVE-2022-31051/
Suggestion
Find the highest published version that wouldn't break the current
^
semver and install that version. Useful commands:Find out:
npm view @babel/core
npm view @babel/core versions
npm view semantic-release
npm view semantic-release versions
Fix:
npm install --save-dev @babel/[email protected]
npm install --save-dev semantic-release@???
The text was updated successfully, but these errors were encountered: