near-api-js
Supply chain provenance
Status for the latest visible version.
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
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 of RPC response data is standard NEAR JSON-RPC API parsing; NEAR protocol returns binary data base64-encoded by design. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of contract code hashes is standard blockchain SDK behavior for NEAR Protocol; not a malicious payload indicator. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): node-fetch is a well-known HTTP library; its use in this SDK is legitimate and the phantom-dep finding is a stable false positive. | ai | |
| phantom-deps | phantom-dep:@noble/curves | AI (phantom-deps): @noble/curves is a well-audited cryptography library; its use in a blockchain SDK is expected and the phantom-dep finding is a stable false positive. | ai | |
| phantom-deps | phantom-dep:http-errors | AI (phantom-deps): http-errors is a standard utility; phantom-dep heuristic fires but this is a stable false positive for this SDK package. | ai | |
| phantom-deps | phantom-dep:near-abi | AI (phantom-deps): near-abi is a NEAR ecosystem package declared as a dependency; phantom-dep heuristic fires because it's not directly imported in source but is a legitimate declared dep for this SDK. | ai | |
| provenance | no-provenance | AI (provenance): near-api-js is the official NEAR Protocol JS SDK published by the NEAR org; lack of Sigstore provenance is not a meaningful risk signal for this well-established package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 6 / 20 | |
| 7.1.1 | 7 / 20 | |
| 7.1.0 | 7 / 20 | |
| 7.0.4 | 7 / 20 | |
| 7.0.3 | 7 / 20 | |
| 7.0.2 | 7 / 20 | |
| 7.0.1 | 7 / 20 | |
| 7.0.0 | 7 / 20 | |
| 6.5.1 | 16 / 11 | |
| 6.5.0 | 16 / 11 | |
| 6.4.1 | 16 / 11 |
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.