Closed mmaurello closed 8 months ago
Latest commit: 88d81ccf808cdce5f591bb68fc4365cd762ca788
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@changesets/cli@2.26.2, npm/@polkadot/api-augment@10.10.1, npm/@polkadot/api@10.10.1, npm/@polkadot/types@10.10.1, npm/@polkadot/util-crypto@12.5.1, npm/@polkadot/util@12.5.1, npm/@types/big.js@6.1.6, npm/@types/jest@29.5.3, npm/@typescript-eslint/eslint-plugin@5.59.9, npm/@typescript-eslint/parser@5.59.9, npm/bun@1.0.20, npm/eslint-config-airbnb-typescript@17.0.0, npm/eslint-config-prettier@8.8.0, npm/eslint-plugin-import@2.27.5, npm/eslint-plugin-jest@27.2.1, npm/eslint-plugin-prettier@4.2.1, npm/eslint@8.42.0, npm/ethers@5.7.2, npm/glob@10.3.3, npm/husky@8.0.3, npm/jest@29.6.1, npm/lint-staged@13.2.3, npm/lru-cache@7.17.0, npm/ts-jest@29.1.0, npm/tsup@6.7.0, npm/turbo@1.10.2, npm/type-fest@3.8.0, npm/typescript@5.1.3, npm/viem@1.10.3
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
Alert | Package | Note | Source |
---|---|---|---|
Native code | npm/bufferutil@4.0.8 |
|
Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.
Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.
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/bufferutil@4.0.8
Description
Update dependencies
Checklist