Skip to content
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

Bump astro from 4.0.7 to 4.0.8 #134

Merged
merged 1 commit into from
Dec 28, 2023

Bump astro from 4.0.7 to 4.0.8

f60651b
Select commit
Loading
Failed to load commit list.
Merged

Bump astro from 4.0.7 to 4.0.8 #134

Bump astro from 4.0.7 to 4.0.8
f60651b
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts failed Dec 28, 2023 in 3m 24s

Pull Request #134 Alerts: Complete with warnings

Report Status Message
PR #134 Alerts ⚠️ Found 1 project alert

Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.

Details

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue Package Version Note Source
Chronological version anomaly astro 4.0.8

Next steps

What is a chronological version anomaly?

Semantic versions published out of chronological order.

This could either indicate dependency confusion or a patched vulnerability.

Take a deeper look at the dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore astro@4.0.8