@getpara/cosmos-wallet-connectors
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this org package; cosmetic only. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 153 versions; org-wide pattern, not a new risk. | ai | |
| phantom-deps | phantom-dep:@leapwallet/cosmos-social-login-capsule-provider | AI (phantom-deps): Listed as a runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped SDK sub-package in an established @getpara ecosystem; missing metadata is a style issue, not malice. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 3.9.0 | 6 / 4 | |
| 3.8.0 | 6 / 4 | |
| 3.7.0 | 6 / 4 | |
| 3.6.0 | 6 / 4 | |
| 3.5.1 | 6 / 4 | |
| 3.5.0 | 6 / 4 | |
| 3.4.0 | 6 / 4 | |
| 3.3.0 | 6 / 4 | |
| 3.2.0 | 6 / 4 | |
| 3.1.0 | 6 / 4 | |
| 3.0.0 | 6 / 4 | |
| 2.32.1 | 6 / 4 | |
| 2.32.0 | 6 / 4 | |
| 2.31.0 | 6 / 4 | |
| 2.28.0 | 6 / 4 | |
| 2.27.0 | 6 / 4 | |
| 2.26.0 | 6 / 4 | |
| 2.25.0 | 6 / 4 | |
| 2.24.0 | 6 / 4 | |
| 2.22.0 | 6 / 4 | |
| 2.21.0 | 6 / 4 | |
| 2.20.0 | 6 / 4 | |
| 2.19.0 | 6 / 4 | |
| 2.18.0 | 6 / 4 | |
| 2.16.0 | 6 / 4 | |
| 2.15.0 | 6 / 4 | |
| 2.12.0 | 6 / 4 | |
| 2.11.0 | 6 / 4 | |
| 2.10.0 | 6 / 4 | |
| 2.8.0 | 6 / 4 | |
| 2.7.0 | 6 / 4 | |
| 2.6.0 | 6 / 4 | |
| 2.5.0 | 6 / 4 | |
| 2.2.0 | 6 / 4 | |
| 2.1.0 | 6 / 4 | |
| 2.0.0 | 6 / 4 |
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.