@getpara/wagmi-v2-connector
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established @getpara org package; missing metadata is a style issue, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all @getpara packages; not a malice signal. | ai | |
| provenance | no-provenance | AI (provenance): @getpara packages consistently lack provenance; not a risk for this org. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 3.10.0 | 2 / 3 | |
| 3.9.0 | 2 / 3 | |
| 3.8.0 | 2 / 3 | |
| 3.7.0 | 2 / 3 | |
| 3.6.0 | 2 / 3 | |
| 3.5.1 | 2 / 3 | |
| 3.5.0 | 2 / 3 | |
| 3.4.0 | 2 / 3 | |
| 3.3.0 | 2 / 3 | |
| 3.2.0 | 2 / 3 | |
| 3.1.0 | 2 / 3 | |
| 3.0.0 | 2 / 3 | |
| 2.32.1 | 2 / 3 | |
| 2.32.0 | 2 / 3 | |
| 2.31.0 | 2 / 3 | |
| 2.28.0 | 2 / 3 | |
| 2.27.0 | 2 / 3 | |
| 2.17.0 | 2 / 3 | |
| 2.16.0 | 2 / 3 | |
| 2.15.0 | 2 / 3 | |
| 2.9.0 | 2 / 3 | |
| 2.4.0 | 2 / 3 | |
| 2.3.0 | 2 / 3 | |
| 2.2.0 | 2 / 3 | |
| 2.1.0 | 2 / 3 | |
| 2.0.0 | 2 / 3 |
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.