@heroku/socksv5
SOCKS protocol version 5 server and client implementations for node.js
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
superhighfivesmaxbeizerjoeyjmoralesmattimohburrowslambaccksigmavirus24sibsondhaulagiricyxdmathieukaratecowboyjmorrellidangazitrasphilcotroelsthomsenfivetanley-herokuheroku-dod-npmheroku-hitfivetanleyjmonsterheroku-tcrayfordcodefingerjsullivandigscyberdeliauhoh-itsmaciekhalorgiumransombriggsalouie-sfdckahlouieeblacknaamanryanbrainardjoshwlewishunterloftisgulopinejingwenomnobleamerinegudmundurappltnraulbdickeyxxxitops
Keywords
proxysockssocks5socksv5
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fixed local submodule loader over a hardcoded array; no arbitrary input path possible. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.0.9 | 1 / 0 |
v0.0.9
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.