Closed franky47 closed 1 year ago
π No new dependency issues detected in pull request
Issue | Status |
---|---|
Install scripts | β 0 issues |
Native code | β 0 issues |
Bin script confusion | β 0 issues |
Bin script shell injection | β 0 issues |
Unresolved require | β 0 issues |
Invalid package.json | β 0 issues |
HTTP dependency | β 0 issues |
Git dependency | β 0 issues |
Potential typo squat | β 0 issues |
Known Malware | β 0 issues |
Telemetry | β 0 issues |
Protestware/Troll package | β 0 issues |
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@2.4.2
Ignoring: es5-ext@0.10.62
Powered by socket.dev
@SocketSecurity ignore es5-ext@0.10.62
ππΊπ¦
:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on npm package (@beta dist-tag)
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on npm package (@beta dist-tag)
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on npm package (@beta dist-tag)
Your semantic-release bot :package::rocket:
In theory, this could help testing versioning strategies with changesets and setting up CD without depending on an immutable (public or private) registry, we could reset the Verdaccio local package database as we ~make mistakes~ learn.