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 wrangler from 3.9.0 to 3.9.1 #15

Merged
merged 1 commit into from
Sep 26, 2023

Bump wrangler from 3.9.0 to 3.9.1

fa0bd14
Select commit
Loading
Failed to load commit list.
Merged

Bump wrangler from 3.9.0 to 3.9.1 #15

Bump wrangler from 3.9.0 to 3.9.1
fa0bd14
Select commit
Loading
Failed to load commit list.
This check has been archived and is scheduled for deletion. Learn more about checks retention
Socket Security / Socket Security: Pull Request Alerts failed Sep 26, 2023 in 11s

Pull Request #15 Alerts: Complete with warnings

Report Status Message
PR #15 Alerts ⚠️ Found 7 project alerts

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 workerd 1.20230922.0
Chronological version anomaly @cloudflare/workerd-linux-64 1.20230922.0
Chronological version anomaly @cloudflare/workerd-linux-arm64 1.20230922.0
Chronological version anomaly @cloudflare/workerd-windows-64 1.20230922.0
Chronological version anomaly @cloudflare/workerd-darwin-64 1.20230922.0
Chronological version anomaly @cloudflare/workerd-darwin-arm64 1.20230922.0
Chronological version anomaly wrangler 3.9.1

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 [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all