search

MetaMask / eth-token-tracker

A JS module for tracking Ethereum token balances over block changes
ISC License
76 stars 43 forks source link

ci: Add workflows for assisted release and publishing #134

Closed legobeat closed 1 month ago

legobeat commented 1 month ago

Before using, a repository administrator will need to configure the following secrets:

socket-security[bot] commented 1 month ago

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

Package New capabilities Transitives Size Publisher
npm/@metamask/auto-changelog@3.4.4 Transitive: environment, filesystem +2 594 kB metamaskbot
npm/cliui@8.0.1 None 0 32.3 kB oss-bot
npm/diff@5.2.0 None 0 429 kB explodingcabbage
npm/execa@5.1.1 environment, shell 0 57.5 kB sindresorhus
npm/get-stream@6.0.1 None 0 12.2 kB sindresorhus
npm/human-signals@2.1.0 None 0 44.3 kB ehmicky
npm/is-stream@2.0.1 None 0 5.93 kB sindresorhus
npm/merge-stream@2.0.0 None 0 4.31 kB stevemao
npm/mimic-fn@2.1.0 None 0 4.46 kB sindresorhus
npm/npm-run-path@4.0.1 environment 0 8.13 kB sindresorhus
npm/onetime@5.1.2 None 0 6.17 kB sindresorhus
npm/prettier@2.8.8 environment, filesystem, unsafe 0 11.2 MB prettier-bot
npm/strip-final-newline@2.0.0 None 0 3.05 kB sindresorhus
npm/yargs-parser@21.1.1 environment, filesystem 0 128 kB oss-bot

View full report↗︎

socket-security[bot] commented 1 month 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/diff@5.2.0, npm/execa@5.1.1, npm/merge-stream@2.0.0

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

legobeat commented 1 month ago 
@SocketSecurity ignore npm/merge-stream@2.0.0
@SocketSecurity ignore npm/diff@5.2.0

new author ok

legobeat commented 1 month ago 
@SocketSecurity ignore npm/execa@5.1.1

shell access ok