@multiversx/sdk-network-providers
1
Versions
—
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
dragosrebegeaarhtudormorarradumojictanghelcipriandccorcoveanuvalentinlupandreibancioiutitellucian.mincu
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is core to blockchain SDK contract response parsing; not a malicious payload indicator. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is standard for blockchain address/data primitives; not a malicious payload indicator. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): buffer is declared as a runtime dependency in package.json and used implicitly via Node.js Buffer API throughout the SDK. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.9.3 | 4 / 11 |
v2.9.3
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.