@agoric/cosmos
Connect JS to the Cosmos blockchain SDK
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): agoricbot addition consistent with org CI automation, no behavior change in diff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer rotation within trusted Agoric org. | ai | |
| npm-metadata | url-dep:esm | AI (npm-metadata): Points to Agoric's own fork, longstanding devDependency. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.35.0 | 3 / 1 | |
| 0.27.1 | 1 / 3 | |
| 0.27.0 | 1 / 3 | |
| 0.26.19 | 1 / 3 | |
| 0.26.18 | 1 / 3 | |
| 0.26.17 | 1 / 3 | |
| 0.26.16 | 1 / 3 | |
| 0.26.15 | 1 / 3 | |
| 0.26.14 | 1 / 3 | |
| 0.26.13 | 1 / 3 | |
| 0.26.12 | 1 / 3 | |
| 0.26.11 | 1 / 3 | |
| 0.26.10 | 1 / 3 | |
| 0.26.9 | 1 / 3 | |
| 0.26.8 | 1 / 3 | |
| 0.26.6 | 1 / 3 | |
| 0.26.5 | 1 / 3 | |
| 0.26.4 | 1 / 3 | |
| 0.26.3 | 1 / 3 | |
| 0.26.2 | 1 / 3 | |
| 0.26.1 | 1 / 3 | |
| 0.26.0 | 1 / 3 | |
| 0.25.4 | 1 / 3 | |
| 0.25.3 | 1 / 3 | |
| 0.25.2 | 1 / 3 | |
| 0.25.1 | 1 / 3 | |
| 0.25.0 | 1 / 3 | |
| 0.24.5 | 1 / 3 | |
| 0.24.4 | 1 / 3 | |
| 0.24.3 | 1 / 3 | |
| 0.24.2 | 1 / 3 | |
| 0.24.1 | 1 / 3 | |
| 0.23.0 | 1 / 3 |
v0.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.