Closed Mrtenz closed 7 months ago
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@lavamoat/aa@3.1.5, npm/@lavamoat/allow-scripts@2.5.1, npm/@metamask/eslint-config-jest@11.1.0, npm/@metamask/eslint-config-nodejs@11.1.0, npm/@metamask/eslint-config-typescript@11.1.0, npm/@metamask/eslint-config@11.1.0, npm/@npmcli/fs@2.1.2, npm/@npmcli/promise-spawn@6.0.2, npm/@npmcli/run-script@6.0.2, npm/abbrev@1.1.1, npm/agentkeepalive@4.5.0, npm/bin-links@4.0.1, npm/cacache@16.1.3, npm/chokidar@3.5.3, npm/eslint-plugin-es@3.0.1, npm/eslint-plugin-node@11.1.0, npm/has@1.0.3, npm/ip@2.0.1, npm/js-sdsl@4.4.0, npm/make-fetch-happen@10.2.1, npm/minipass-collect@1.0.2, npm/minipass-fetch@2.1.2, npm/node-gyp@9.4.1, npm/nopt@6.0.0, npm/read-package-json-fast@3.0.2, npm/socks-proxy-agent@7.0.0, npm/ssri@9.0.1, npm/unique-filename@2.0.1, npm/unique-slug@3.0.0, npm/which@3.0.1
👍 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/@lavamoat/preinstall-always-fail@2.0.0
, npm/@npmcli/agent@2.2.1
, npm/abbrev@2.0.0
, npm/agent-base@7.1.0
, npm/debug@2.6.9
, npm/esbuild@0.19.12
, npm/foreground-child@3.1.1
, npm/mz@2.7.0
, npm/nopt@7.2.0
, npm/normalize-package-data@6.0.0
, npm/socks-proxy-agent@8.0.2
, npm/source-map@0.8.0-beta.0
, npm/tree-kill@1.2.2
, npm/tsup@7.3.0
, npm/validate-npm-package-name@5.0.0
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.
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.
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
@SocketSecurity ignore npm/debug@2.6.9 @SocketSecurity ignore npm/agent-base@7.1.0 @SocketSecurity ignore npm/mz@2.7.0 @SocketSecurity ignore npm/@npmcli/agent@2.2.1 @SocketSecurity ignore npm/socks-proxy-agent@8.0.2
Network access is ok. Not used in production.
@SocketSecurity ignore npm/validate-npm-package-name@5.0.0 @SocketSecurity ignore npm/nopt@7.2.0 @SocketSecurity ignore npm/abbrev@2.0.0 @SocketSecurity ignore npm/source-map@0.8.0-beta.0 @SocketSecurity ignore npm/normalize-package-data@6.0.0
New authors seem ok.
@SocketSecurity ignore npm/foreground-child@3.1.1 @SocketSecurity ignore npm/tree-kill@1.2.2
Shell access ok. Not used in production.
@SocketSecurity ignore npm/esbuild@0.19.12
Network / shell access is expected.
@SocketSecurity ignore npm/tsup@7.3.0
Deprecated is ok. Shouldn't be an issue in our case.
@SocketSecurity ignore npm/@lavamoat/preinstall-always-fail@2.0.0
Script is expected.
This updates the repository to match the module template as of February 2024. This repo hasn't been updated in a while, so there's quite a few changes. The most notable changes are:
.nvmrc
Node versions, to reduce the number of jobs.tsup
, and includes a ESM build.