Bump astro from 3.2.4 to 3.3.0 #24
Pull Request #24 Alerts: Complete with warnings
| Report | Status | Message |
|---|---|---|
| PR #24 Alerts | Found 59 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 | @types/hast | 3.0.1 |
|
|
| Long strings | shikiji | 0.6.10 |
|
|
| No v1 | shikiji | 0.6.10 |
|
|
| No v1 | tsconfck | 3.0.0-next.9 |
|
|
| Unpublished package | @astrojs/markdown-remark | 3.3.0 |
|
|
| Unpublished package | astro | 3.3.0 |
|
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's wrong with long strings?
Contains long string literals, which may be a sign of obfuscated or packed code.
Avoid publishing or consuming obfuscated or bundled code. It makes dependencies difficult to audit and undermines the module resolution system.
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.
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 foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore shikiji@0.6.10@SocketSecurity ignore tsconfck@3.0.0-next.9@SocketSecurity ignore @astrojs/markdown-remark@3.3.0@SocketSecurity ignore astro@3.3.0@SocketSecurity ignore @types/hast@3.0.1