-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
devDeps: @lavamoat/allow-scripts@2.0.3->2.3.1 #20018
devDeps: @lavamoat/allow-scripts@2.0.3->2.3.1 #20018
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
d94372e
to
6918488
Compare
re (endpoint returns |
858554b
to
da1954f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
da1954f
to
0532a25
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as well.
25650d4
to
f0c9bb5
Compare
1478a53
to
1a0f742
Compare
1a0f742
to
0e41e0c
Compare
Hmm, another audit failure |
0e41e0c
to
b5e1d1c
Compare
Yes:
|
289d637
to
35a7a32
Compare
linked issue seems irrelevant - underlying error is different
we're likely getting a non json error message from a json endpoint |
What do you see as different here? Both are due to the 400 from the npm audit backend. |
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhy is contributor and author data important?Package does not specify a list of contributors or an author in package.json. Add a author field or contributors array to package.json. What are unmaintained packages?Package has not been updated in more than a year and may be unmaintained. Problems with the package may go unaddressed. Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
e150a72
to
cddc9af
Compare
cddc9af
to
39958dd
Compare
39958dd
to
6d6f055
Compare
Explanation
Maintenance update; security fixes
Manual Testing Steps
Pre-merge author checklist
Pre-merge reviewer checklist