@near-js/accounts No license 21 versions

@near-js/accounts

npm

21

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

nearndyfrolnearmorgan

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:lru_map	AI (phantom-deps): Declared runtime dep; likely used transitively or in compiled output not directly imported in source.	ai	2026/05/24
phantom-deps	phantom-dep:@noble/hashes	AI (phantom-deps): Declared runtime dep; used via config or transitive imports in this NEAR crypto package.	ai	2026/05/24
phantom-deps	phantom-dep:@near-js/tokens	AI (phantom-deps): Same-org package; stable false positive for this monorepo package.	ai	2026/05/24
phantom-deps	phantom-dep:is-my-json-valid	AI (phantom-deps): Declared runtime dep; used in config/validation paths not directly imported at top level.	ai	2026/05/24
semgrep	semgrep:base64-decode	AI (semgrep): Decoding WASM contract code from base64 for local view execution — expected SDK functionality.	ai	2026/05/23
phantom-deps	phantom-dep:borsh	AI (phantom-deps): borsh is a declared runtime dependency used transitively; phantom-dep heuristic is a false positive here.	ai	2026/05/23
semgrep	semgrep:hex-decode	AI (semgrep): Decoding contract code hash from hex string — standard blockchain SDK operation, not malicious.	ai	2026/05/23

Versions (showing 21 of 21)

Version	Deps	Published
2.5.1	14 / 12	2025-11-06
2.5.0	13 / 13	2025-11-03
2.4.1	13 / 13	2025-11-03
2.4.0	13 / 13	2025-10-26
2.3.4	13 / 13	2025-10-16
2.3.3	13 / 13	2025-10-01
2.3.2	13 / 13	2025-09-24
2.3.1	13 / 13	2025-09-10
2.3.0	13 / 13	2025-09-03
2.2.6	13 / 13	2025-08-26
2.2.5	13 / 13	2025-08-06
2.2.4	13 / 13	2025-07-24
2.2.3	13 / 13	2025-07-21
2.2.2	13 / 13	2025-07-09
2.2.1	13 / 13	2025-07-07
2.2.0	13 / 13	2025-07-04
2.1.0	13 / 13	2025-06-16
2.0.3	13 / 14	2025-06-11
2.0.2	13 / 14	2025-05-30
2.0.1	13 / 14	2025-05-21
2.0.0	13 / 14	2025-05-21

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.

v2.4.1

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.

v2.4.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.

v2.3.4

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.

v2.3.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.

v2.3.2

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.

v2.3.1

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.

v2.3.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.

v2.2.6

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.

v2.2.5

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.

v2.2.4

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.

v2.2.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.

v2.2.2

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.

v2.2.1

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.

v2.2.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.

v2.1.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.

v2.0.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.

v2.0.2

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.

v2.0.1

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.

v2.0.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.