← Home

@near-js/transactions

Functions and data types for transactions on NEAR

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

Maintainers

nearndyfrolnearmorgan

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@near-js/signers AI (dependencies): @near-js/signers is a sibling package in the same org scope, published by the same trusted NEAR team. The unvetted flag reflects pipeline ordering, not a genuine supply-chain risk. ai
dependencies unvetted-dep:@near-js/types AI (dependencies): First-party @near-js org dependency published in coordinated monorepo releases; stable pattern across all versions of this package. ai
dependencies unvetted-dep:@near-js/utils AI (dependencies): First-party @near-js org dependency published in coordinated monorepo releases; stable pattern across all versions of this package. ai
dependencies unvetted-dep:@near-js/crypto AI (dependencies): First-party @near-js org dependency published in coordinated monorepo releases; stable pattern across all versions of this package. ai
provenance no-provenance AI (provenance): Established NEAR JS SDK package with strong publisher track record; lack of provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:@noble/hashes AI (phantom-deps): @noble/hashes is a legitimate declared dependency used for cryptographic hashing; referenced in config files is expected for this type of package. ai
phantom-deps phantom-dep:@near-js/utils AI (phantom-deps): Same-org sibling package in the @near-js monorepo; phantom detection is a false positive for intra-monorepo dependencies. ai

Versions (showing 40 of 40)

Version Deps Published
2.5.1 5 / 7
2.5.0 5 / 7
2.4.1 5 / 7
2.4.0 5 / 7
2.3.4 5 / 7
2.3.3 5 / 7
2.3.2 5 / 7
2.3.1 5 / 7
2.3.0 5 / 7
2.2.6 5 / 7
2.2.5 5 / 7
2.2.4 5 / 7
2.2.3 5 / 7
2.2.2 5 / 7
2.2.1 5 / 7
2.2.0 5 / 7
2.1.0 5 / 7
2.0.3 5 / 8
2.0.2 5 / 8
2.0.1 5 / 8
2.0.0 5 / 8
1.3.3 6 / 8
1.3.2 6 / 8
1.3.1 6 / 8
1.3.0 6 / 8
1.2.3 6 / 5
1.2.2 6 / 5
1.2.1 6 / 5
1.2.0 6 / 5
1.1.2 7 / 5
1.1.1 7 / 5
1.1.0 7 / 5
1.0.1 7 / 5
1.0.0 7 / 5
0.2.1 7 / 5
0.2.0 7 / 5
0.1.1 7 / 5
0.1.0 7 / 5
0.0.2 7 / 5
0.0.1 7 / 5

v2.5.1

1 finding
INFO No provenance attestation provenance

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