← Home

@multiversx/sdk-network-providers

npm
9
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

dragosrebegeaarhtudormorarradumojictanghelcipriandccorcoveanuvalentinlupandreibancioiutitellucian.mincu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 9 of 9)

Version Deps Published
2.9.3 4 / 11
2.9.2 4 / 11
2.9.1 4 / 11
2.9.0 4 / 11
2.8.0 4 / 11
2.7.1 4 / 11
2.7.0 4 / 11
2.6.0 4 / 11
2.5.0 4 / 11

v2.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.5.0

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.