search

swc-project / pkgs

node.js packages for SWC
59 stars 19 forks source link

chore: Fix publish issues #15

Closed kdy1 closed 9 months ago

kdy1 commented 9 months ago
changeset-bot[bot] commented 9 months ago

⚠️ No Changeset found

Latest commit: 22a0bd4d7960ad3673575febd687fbfccc8ca8c5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

socket-security[bot] commented 9 months ago

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@swc/core@1.3.107 environment, filesystem, shell +2 399 kB kdy1

🚮 Removed packages: npm/@swc/cli@0.1.44, npm/swc-loader@0.2.3

View full report↗︎

socket-security[bot] commented 9 months ago

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@swc/core@1.3.107

View full report↗︎

Next steps

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 ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

kdy1 commented 9 months ago

@SocketSecurity ignore npm/@swc/core@1.3.107