Bump astro from 4.0.6 to 4.0.7 #81
Pull Request #81 Alerts: Complete with warnings
| Report | Status | Message |
|---|---|---|
| PR #81 Alerts | Found 8 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 |
|---|---|---|---|---|
| Major refactor | @firebase/auth | 1.5.1 |
|
|
| Mixed license | @protobufjs/float | 1.0.2 |
|
|
| Mixed license | domhandler | 5.0.3 |
|
|
| Modified license | human-signals | 5.0.0 |
|
|
| Unpublished package | astro | 4.0.7 |
|
Next steps
What is a major refactor?
Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Consider waiting before upgrading to see if any issues are discovered, or be prepared to scrutinize any bugs or subtle changes the major refactor may bring. Publishers my consider publishing beta versions of major refactors to limit disruption to parties interested in the new changes.
What is a mixed license?
(Experimental) Package contains multiple licenses.
A new version of the package should be published that includes a single license. Consumers may seek clarification from the package author. Ensure that the license details are consistent across the LICENSE file, package.json license field and license details mentioned in the README.
What is a modified license?
(Experimental) Package contains a modified version of an SPDX license. Please read carefully before using this code.
Packages should avoid making modifications to standard licenses.
What are unpublished packages?
Package version was not found on the registry. It may exist on a different registry and need to be configured to pull from that registry.
Packages can be removed from the registry by manually un-publishing, a security issue removal, or may simply never have been published to the registry. Reliance on these packages will cause problem when they are not found.
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
@SocketSecurity ignore [email protected]@SocketSecurity ignore @protobufjs/[email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore @firebase/[email protected]@SocketSecurity ignore [email protected]