← Home

@getpara/solana-web3.js-v1-integration

npm
38
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

nityasnsquaretboschphtoweljordymcnabkwi25

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Part of established @getpara SDK suite with 151 versions; sparse metadata is a consistent pattern, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Consistent across all versions of this package; not indicative of malice. ai
provenance no-provenance AI (provenance): No provenance across all versions; publisher has 52 approved packages with same pattern. ai

Versions (showing 38 of 38)

Version Deps Published
3.10.0 1 / 2
3.9.0 1 / 2
3.8.0 1 / 2
3.7.0 1 / 2
3.6.0 1 / 2
3.5.1 1 / 2
3.5.0 1 / 2
3.4.0 1 / 2
3.3.0 1 / 2
3.2.0 1 / 2
3.1.0 1 / 2
3.0.0 1 / 2
2.32.1 1 / 2
2.32.0 1 / 2
2.31.0 1 / 2
2.28.0 1 / 2
2.27.0 1 / 2
2.26.0 1 / 2
2.25.0 1 / 2
2.24.0 1 / 2
2.23.0 1 / 2
2.22.0 1 / 2
2.21.0 1 / 2
2.20.0 1 / 2
2.19.0 1 / 2
2.18.0 1 / 2
2.16.0 1 / 2
2.15.0 1 / 2
2.12.0 1 / 2
2.11.0 1 / 2
2.10.0 1 / 2
2.8.0 1 / 2
2.7.0 1 / 2
2.6.0 1 / 2
2.5.0 1 / 2
2.2.0 1 / 2
2.1.0 1 / 2
2.0.0 1 / 2

v3.10.0

1 finding
INFO No provenance attestation provenance

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

v3.9.0

1 finding
INFO No provenance attestation provenance

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

v3.8.0

1 finding
INFO No provenance attestation provenance

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

v3.7.0

1 finding
INFO No provenance attestation provenance

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

v3.6.0

1 finding
INFO No provenance attestation provenance

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

v3.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.

v3.5.0

1 finding
INFO No provenance attestation provenance

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