@chain-registry/utils
Chain Registry Utils
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@keplr-wallet/crypto | AI (dependencies): @keplr-wallet/crypto is a well-known cryptographic library from the Keplr wallet team, a major Cosmos ecosystem project. Its use in chain-registry utils is expected and appropriate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of a large, established monorepo (cosmology-tech/chain-registry) by a trusted publisher; sparse README and missing keywords are cosmetic, not indicative of spam. | ai | |
| dependencies | unvetted-dep:@chain-registry/types | AI (dependencies): @chain-registry/types is a sibling package in the same hyperweb-io/chain-registry monorepo, published by the same trusted author (pyramation). Unvetted status is transient and expected for co-released packages. | ai | |
| dependencies | unvetted-dep:chain-registry | AI (dependencies): chain-registry is a sibling package in the same hyperweb-io/chain-registry monorepo, published by the same trusted author (pyramation). Unvetted status is transient and expected for co-released packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): chain-registry is a sibling package in the same hyperweb-io/chain-registry monorepo, published by the same maintainer. Intra-monorepo dependency additions are expected and low-risk for this package. | ai | |
| phantom-deps | phantom-dep:chain-registry | AI (phantom-deps): chain-registry is a sibling monorepo package; indirect/config usage without direct import is a common pattern in this ecosystem. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Standard npm pattern referencing a LICENSE file; common in open-source projects and not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread provenance adoption; publisher has strong track record. Stable false positive for this package. | ai |
Versions (showing 51 of 827)
| Version | Deps | Published |
|---|---|---|
| 2.0.213 | 4 / 1 | |
| 2.0.212 | 4 / 1 | |
| 2.0.211 | 4 / 1 | |
| 2.0.210 | 4 / 1 | |
| 2.0.209 | 4 / 1 | |
| 2.0.208 | 4 / 1 | |
| 2.0.207 | 4 / 1 | |
| 2.0.206 | 4 / 1 | |
| 2.0.205 | 4 / 1 | |
| 2.0.204 | 4 / 1 | |
| 2.0.203 | 4 / 1 | |
| 2.0.202 | 4 / 1 | |
| 2.0.201 | 4 / 1 | |
| 2.0.200 | 4 / 1 | |
| 2.0.199 | 4 / 1 | |
| 2.0.198 | 4 / 1 | |
| 2.0.197 | 4 / 1 | |
| 2.0.196 | 4 / 1 | |
| 2.0.195 | 4 / 1 | |
| 2.0.194 | 4 / 1 | |
| 2.0.193 | 4 / 1 | |
| 2.0.192 | 4 / 1 | |
| 2.0.191 | 4 / 1 | |
| 2.0.190 | 4 / 1 | |
| 2.0.189 | 4 / 1 | |
| 2.0.188 | 4 / 1 | |
| 2.0.187 | 4 / 1 | |
| 2.0.186 | 4 / 1 | |
| 2.0.185 | 4 / 1 | |
| 2.0.184 | 4 / 1 | |
| 2.0.183 | 4 / 1 | |
| 2.0.182 | 4 / 1 | |
| 2.0.181 | 4 / 1 | |
| 2.0.180 | 4 / 1 | |
| 2.0.179 | 4 / 1 | |
| 2.0.178 | 4 / 1 | |
| 2.0.177 | 4 / 1 | |
| 2.0.176 | 4 / 1 | |
| 2.0.175 | 4 / 1 | |
| 2.0.174 | 4 / 1 | |
| 2.0.173 | 4 / 1 | |
| 2.0.172 | 4 / 1 | |
| 2.0.171 | 4 / 1 | |
| 2.0.170 | 4 / 1 | |
| 2.0.169 | 4 / 1 | |
| 2.0.167 | 4 / 1 | |
| 2.0.166 | 4 / 1 | |
| 2.0.165 | 4 / 1 | |
| 2.0.164 | 4 / 1 | |
| 2.0.163 | 4 / 1 | |
| 2.0.162 | 4 / 1 |
v2.0.213
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.212
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.211
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.210
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.209
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.208
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.207
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.206
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.205
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.204
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.203
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.202
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.201
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.200
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.199
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.198
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.197
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.196
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.195
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.193
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.192
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.190
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.