chain-registry
Cosmos chain registry ⚛️
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 |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): chain-registry is a static data package listing blockchain RPC endpoints; raw IP addresses are legitimate devnet/testnet endpoint addresses, not malicious links. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): chain-registry lists hundreds of blockchain provider endpoints; non-standard TLDs (.xyz, etc.) are common among blockchain infrastructure providers and are static data strings, not executed code. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher (pyramation, 7+ years, 20 approved packages); absence of Sigstore provenance is common and not a meaningful risk signal here. | ai |
Versions (showing 80 of 1185)
| Version | Deps | Published |
|---|---|---|
| 1.18.1 | 2 / 26 | |
| 1.18.0 | 2 / 26 | |
| 1.17.1 | 2 / 26 | |
| 1.17.0 | 2 / 26 | |
| 1.16.0 | 2 / 26 | |
| 1.15.0 | 2 / 26 | |
| 1.14.0 | 2 / 26 | |
| 1.13.0 | 2 / 26 | |
| 1.12.0 | 2 / 26 | |
| 1.11.1 | 2 / 26 | |
| 1.11.0 | 2 / 26 | |
| 1.10.0 | 2 / 26 | |
| 1.9.0 | 2 / 26 | |
| 1.8.0 | 2 / 26 | |
| 1.7.0 | 2 / 26 | |
| 1.6.1 | 2 / 26 | |
| 1.6.0 | 2 / 26 | |
| 1.5.0 | 2 / 26 | |
| 1.4.0 | 2 / 26 | |
| 1.3.1 | 2 / 26 | |
| 1.3.0 | 2 / 26 | |
| 1.2.0 | 2 / 26 | |
| 1.1.0 | 2 / 26 | |
| 1.0.1 | 2 / 26 | |
| 1.0.0 | 2 / 26 | |
| 0.14.0 | 2 / 26 | |
| 0.13.2 | 2 / 26 | |
| 0.13.1 | 2 / 26 | |
| 0.13.0 | 2 / 26 | |
| 0.11.0 | 2 / 26 | |
| 0.10.3 | 2 / 26 | |
| 0.10.2 | 2 / 26 | |
| 0.10.1 | 2 / 26 | |
| 0.10.0 | 2 / 26 | |
| 0.9.3 | 2 / 26 | |
| 0.9.2 | 2 / 26 | |
| 0.9.1 | 2 / 26 | |
| 0.9.0 | 2 / 26 | |
| 0.8.1 | 2 / 26 | |
| 0.8.0 | 2 / 26 | |
| 0.7.0 | 2 / 26 | |
| 0.6.3 | 2 / 26 | |
| 0.6.2 | 2 / 26 | |
| 0.6.1 | 2 / 26 | |
| 0.6.0 | 2 / 26 | |
| 0.5.1 | 1 / 26 | |
| 0.5.0 | 1 / 26 | |
| 0.4.1 | 1 / 26 | |
| 0.4.0 | 1 / 26 | |
| 0.3.1 | 1 / 26 | |
| 0.3.0 | 1 / 25 | |
| 0.2.1 | 1 / 25 | |
| 0.2.0 | 1 / 25 | |
| 0.1.0 | 1 / 25 | |
| 0.0.41 | 1 / 27 | |
| 0.0.40 | 1 / 27 | |
| 0.0.39 | 1 / 27 | |
| 0.0.38 | 1 / 27 | |
| 0.0.37 | 1 / 27 | |
| 0.0.36 | 1 / 27 | |
| 0.0.35 | 1 / 27 | |
| 0.0.34 | 1 / 27 | |
| 0.0.33 | 1 / 27 | |
| 0.0.32 | 1 / 27 | |
| 0.0.31 | 1 / 27 | |
| 0.0.30 | 1 / 27 | |
| 0.0.29 | 1 / 27 | |
| 0.0.28 | 1 / 27 | |
| 0.0.27 | 1 / 27 | |
| 0.0.26 | 1 / 27 | |
| 0.0.25 | 1 / 27 | |
| 0.0.24 | 1 / 27 | |
| 0.0.23 | 1 / 27 | |
| 0.0.22 | 1 / 27 | |
| 0.0.21 | 1 / 23 | |
| 0.0.20 | 1 / 23 | |
| 0.0.19 | 1 / 23 | |
| 0.0.18 | 1 / 23 | |
| 0.0.17 | 1 / 23 | |
| 0.0.15 | 1 / 23 |
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.