@near-js/utils
Common methods and constants for the NEAR API JavaScript client
Supply chain provenance
Status for the latest visible version.
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
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 in getTransactionLastResult is standard NEAR protocol behavior — the RPC returns SuccessValue as Base64. This is a legitimate SDK utility, not a malicious payload. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 50 versions and 363k weekly downloads; lack of provenance attestation is not a meaningful risk signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Official @near-js scoped monorepo package; missing repo/keywords is normal for sub-packages, high downloads/inbound edges confirm legitimacy. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 2.5.1 | 4 / 7 | |
| 2.5.0 | 4 / 7 | |
| 2.4.1 | 4 / 7 | |
| 2.4.0 | 4 / 7 | |
| 2.3.4 | 4 / 7 | |
| 2.3.3 | 4 / 7 | |
| 2.3.2 | 4 / 7 | |
| 2.3.1 | 4 / 7 | |
| 2.3.0 | 4 / 7 | |
| 2.2.6 | 4 / 7 | |
| 2.2.5 | 4 / 7 | |
| 2.2.4 | 4 / 7 | |
| 2.2.3 | 4 / 7 | |
| 2.2.2 | 4 / 7 | |
| 2.2.1 | 4 / 7 | |
| 2.2.0 | 4 / 7 | |
| 2.1.0 | 4 / 7 | |
| 2.0.3 | 4 / 8 | |
| 2.0.2 | 4 / 8 | |
| 2.0.1 | 4 / 7 | |
| 2.0.0 | 4 / 7 | |
| 1.1.0 | 4 / 7 | |
| 1.0.1 | 4 / 7 | |
| 1.0.0 | 4 / 7 | |
| 0.3.0 | 4 / 4 | |
| 0.2.2 | 4 / 4 | |
| 0.2.1 | 4 / 4 | |
| 0.2.0 | 4 / 4 | |
| 0.1.0 | 5 / 4 | |
| 0.0.5 | 5 / 4 | |
| 0.0.4 | 4 / 4 | |
| 0.0.3 | 4 / 4 | |
| 0.0.2 | 4 / 4 | |
| 0.0.1 | 4 / 4 |
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): No repo/homepage, inflated semver on first publish, and no keywords — combined with unknown publisher strongly indicates counterfeit/squatted package impersonating the legitimate N) Matched 3 signal(s), weighted score 4: • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): No repo/homepage, inflated semver on first publish, and no keywords — combined with unknown publisher strongly indicates counterfeit/squatted package impersonating the legitimate N) Matched 3 signal(s), weighted score 4: • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): No repo/homepage, inflated semver on first publish, and no keywords — combined with unknown publisher strongly indicates counterfeit/squatted package impersonating the legitimate N) Matched 3 signal(s), weighted score 4: • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): No repo/homepage, inflated semver on first publish, and no keywords — combined with unknown publisher strongly indicates counterfeit/squatted package impersonating the legitimate N) Matched 3 signal(s), weighted score 4: • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.