← Home

@getpara/wagmi-v2-integration

npm
45
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
npm-metadata no-description AI (npm-metadata): Stable pattern across this package family; not indicative of malice. ai
provenance no-provenance AI (provenance): Consistent across all versions of this package; low-risk SDK integration. ai
bogus-package bogus-package AI (bogus-package): Thin integration wrapper in a versioned @getpara monorepo; sparse metadata is structural, not spam. ai

Versions (showing 45 of 45)

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

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.