@chain-registry/juno
Chain Registry info for Juno
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pino | AI (typosquat): @chain-registry/juno is a scoped Cosmos chain-registry data package with no relation to the pino logger; the Levenshtein match is purely coincidental and will never be a real typosquat signal for this package. | ai |
Versions (showing 7 of 418)
| Version | Deps | Published |
|---|---|---|
| 1.70.200 | 1 / 1 | |
| 1.70.199 | 1 / 1 | |
| 1.70.198 | 1 / 1 | |
| 1.70.197 | 1 / 1 | |
| 1.70.196 | 1 / 1 | |
| 1.70.195 | 1 / 1 | |
| 1.70.194 | 1 / 1 |
v1.70.200
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.199
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.198
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.197
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.196
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.70.194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.