Bump firebase from 10.5.0 to 10.5.2 #43
Pull Request #43 Alerts: Complete with warnings
| Report | Status | Message |
|---|---|---|
| PR #43 Alerts | Found 53 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.
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.
What is environment variable access?
Package accesses environment variables, which may be a sign of credential stuffing or data theft.
Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.
What is network access?
This module accesses the network.
Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
What is wrong with semver < v1?
Package is not semver >=1. This means it is not stable and does not support ^ ranges.
If the package sees any general use, it should begin releasing at version 1.0.0 or later to benefit from semver.
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 @firebase/[email protected]@SocketSecurity ignore @firebase/[email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore @firebase/[email protected]@SocketSecurity ignore @firebase/[email protected]@SocketSecurity ignore @firebase/[email protected]@SocketSecurity ignore @firebase/[email protected]@SocketSecurity ignore @firebase/[email protected]