Closed goosewobbler closed 1 year ago
New dependency changes detected. Learn more about Socket for GitHub ↗︎
👍 No new dependency issues detected in pull request
To ignore an alert, reply with a comment starting with @SocketSecurity ignore
followed by a space separated list of package-name@version
specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@*
or ignore all packages with @SocketSecurity ignore-all
Ignoring: @swc/core@1.3.62
Issue | Status |
---|---|
Install scripts | ✅ 0 issues |
Native code | ✅ 0 issues |
Bin script shell injection | ✅ 0 issues |
Unresolved require | ✅ 0 issues |
Invalid package.json | ✅ 0 issues |
HTTP dependency | ✅ 0 issues |
Git dependency | ✅ 0 issues |
Potential typo squat | ✅ 0 issues |
Known Malware | ✅ 0 issues |
Telemetry | ✅ 0 issues |
Protestware/Troll package | ✅ 0 issues |
📊 Modified Dependency Overview:
➕ Added Package | Capability Access | +/- Transitive Count |
Publisher |
---|---|---|---|
@ethereumjs/tx@4.1.2 | network | +10 |
holgerd77 |
https-browserify@1.0.0 | network | +0 |
feross |
stream-http@3.2.0 | network | +2 |
jhiesey |
browserify-zlib@0.2.0 | None | +0 |
dignifiedquire |
@ethereumjs/common@3.1.2 | network | +9 |
holgerd77 |
🚮 Removed packages: typescript@4.9.5
@SocketSecurity ignore @swc/core@1.3.62
Notable Updates:
electron
v25 (Chromium 114.0.5735.45, Node 18.14.0) - changelogs:@parcel/*
v2.9.1 - now correctly usesbuffer
v6 polyfill, fixes issue around installingbuffer
when running prodtypescript
v5.1rimraf
v5.0.1 - works as before vianpx
styled-components
v6@ethereumjs/util
in the renderer process requires additional polyfills:browserify-zlib
https-browserify
stream-http
No upgrade (ESM only)
node-fetch
ipfs-unixfs-importer
query-string
conf
No upgrade (significant code changes required)
ethers