Closed Shaptic closed 8 months ago
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@babel/cli@7.23.9, npm/@babel/compat-data@7.23.5, npm/@babel/core@7.23.9, npm/@babel/eslint-parser@7.23.10, npm/@babel/helper-plugin-utils@7.22.5, npm/@babel/parser@7.23.9, npm/@babel/plugin-transform-optional-chaining@7.23.4, npm/@babel/preset-env@7.23.9, npm/@babel/template@7.23.9, npm/@babel/types@7.23.9, npm/@jridgewell/gen-mapping@0.3.3, npm/@jridgewell/resolve-uri@3.1.1, npm/@jridgewell/trace-mapping@0.3.22, npm/@types/eslint@8.56.2, npm/@types/node@20.11.17, npm/@webassemblyjs/ast@1.11.6, npm/@webassemblyjs/wasm-parser@1.11.6, npm/available-typed-arrays@1.0.6, npm/browserslist@4.22.3, npm/call-bind@1.0.6, npm/core-js-compat@3.35.1, npm/define-data-property@1.1.3, npm/elliptic@6.5.4, npm/es-abstract@1.22.3, npm/eslint-webpack-plugin@4.0.1, npm/eslint@8.56.0, npm/flatted@3.2.9, npm/has-property-descriptors@1.0.1, npm/istanbul-reports@3.1.6, npm/karma-firefox-launcher@2.1.2, npm/karma@6.4.2, npm/parse-asn1@5.1.6, npm/sodium-native@4.0.8, npm/typescript@5.3.3, npm/webpack@5.90.1, npm/which-typed-array@1.1.14
🚨 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 |
---|---|---|---|
Debug access | npm/asn1.js@4.10.1 |
| |
Debug access | npm/enhanced-resolve@5.16.0 |
|
|
Uses debug, reflection and dynamic code execution features.
Removing the use of debug will reduce the risk of any reflection and dynamic code execution.
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/asn1.js@4.10.1
@SocketSecurity ignore npm/enhanced-resolve@5.16.0
is there an approach to test/verify a base version pr branch against js-stellar-sdk locally first, i.e. @stellar/stellar-base: https://github.com/stellar/js-stellar-base.git#v11.0.1
, just to confirm js-stellar-sdk builds, passes?
@sreuland good idea! I just confirmed that it worked locally with a gitref to 00cf120
.
Size Change: -198 B (0%)
Total Size: 3.2 MB
dist/stellar-base.js
dist/stellar-base.min.js
compressed-size-action