@cosmos-kit/react
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cosmos-kit/core | AI (dependencies): Sibling package in the same cosmos-kit monorepo; stable dependency relationship across all versions. | ai | |
| dependencies | unvetted-dep:@cosmos-kit/react-lite | AI (dependencies): Sibling package in the same cosmos-kit monorepo; stable dependency relationship across all versions. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 2.24.1 | 4 / 3 | |
| 2.24.0 | 4 / 3 | |
| 2.23.0 | 4 / 3 | |
| 2.22.7 | 4 / 3 | |
| 2.22.6 | 4 / 3 | |
| 2.22.5 | 4 / 3 | |
| 2.22.4 | 4 / 3 | |
| 2.22.3 | 4 / 3 | |
| 2.22.2 | 4 / 3 | |
| 2.22.1 | 4 / 3 | |
| 2.22.0 | 4 / 3 | |
| 2.21.7 | 4 / 3 | |
| 2.21.6 | 4 / 3 | |
| 2.21.5 | 4 / 3 | |
| 2.21.4 | 4 / 3 | |
| 2.21.2 | 4 / 3 | |
| 2.21.1 | 4 / 2 | |
| 2.21.0 | 4 / 2 | |
| 2.20.1 | 4 / 2 | |
| 2.20.0 | 4 / 2 | |
| 2.19.0 | 4 / 2 | |
| 2.18.0 | 4 / 2 | |
| 2.17.2 | 4 / 2 | |
| 2.17.1 | 4 / 2 | |
| 2.17.0 | 4 / 2 | |
| 2.16.0 | 4 / 2 | |
| 2.15.0 | 4 / 2 | |
| 2.14.1 | 4 / 2 | |
| 2.14.0 | 4 / 2 | |
| 2.13.0 | 4 / 2 | |
| 2.12.0 | 3 / 3 |
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.