@chain-registry/keplr
Chain Registry to Keplr
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): @types/semver is a TypeScript type package loaded by convention in TS projects; not directly imported but legitimately declared as a dep. | ai | |
| phantom-deps | phantom-dep:chain-registry | AI (phantom-deps): chain-registry is the core data package from the same org; referenced in config files as expected for this integration package. | ai | |
| phantom-deps | phantom-dep:@keplr-wallet/crypto | AI (phantom-deps): @keplr-wallet/crypto is a peer/transitive dep referenced in config; standard pattern for Keplr wallet integration packages. | ai |
Versions (showing 100 of 434)
| Version | Deps | Published |
|---|---|---|
| 2.0.214 | 6 / 0 | |
| 2.0.213 | 6 / 0 | |
| 2.0.212 | 6 / 0 | |
| 2.0.211 | 6 / 0 | |
| 2.0.210 | 6 / 0 | |
| 2.0.209 | 6 / 0 | |
| 2.0.208 | 6 / 0 | |
| 2.0.207 | 6 / 0 | |
| 2.0.206 | 6 / 0 | |
| 2.0.205 | 6 / 0 | |
| 2.0.204 | 6 / 0 | |
| 2.0.203 | 6 / 0 | |
| 2.0.202 | 6 / 0 | |
| 2.0.201 | 6 / 0 | |
| 2.0.200 | 6 / 0 | |
| 2.0.199 | 6 / 0 | |
| 2.0.198 | 6 / 0 | |
| 2.0.197 | 6 / 0 | |
| 2.0.196 | 6 / 0 | |
| 2.0.195 | 6 / 0 | |
| 2.0.194 | 6 / 0 | |
| 2.0.193 | 6 / 0 | |
| 2.0.192 | 6 / 0 | |
| 2.0.191 | 6 / 0 | |
| 2.0.190 | 6 / 0 | |
| 2.0.189 | 6 / 0 | |
| 2.0.188 | 6 / 0 | |
| 2.0.187 | 6 / 0 | |
| 2.0.186 | 6 / 0 | |
| 2.0.185 | 6 / 0 | |
| 2.0.184 | 6 / 0 | |
| 2.0.183 | 6 / 0 | |
| 2.0.182 | 6 / 0 | |
| 2.0.181 | 6 / 0 | |
| 2.0.180 | 6 / 0 | |
| 2.0.179 | 6 / 0 | |
| 2.0.178 | 6 / 0 | |
| 2.0.177 | 6 / 0 | |
| 2.0.176 | 6 / 0 | |
| 2.0.175 | 6 / 0 | |
| 2.0.174 | 6 / 0 | |
| 2.0.173 | 6 / 0 | |
| 2.0.172 | 6 / 0 | |
| 2.0.171 | 6 / 0 | |
| 2.0.170 | 6 / 0 | |
| 2.0.169 | 6 / 0 | |
| 2.0.167 | 6 / 0 | |
| 2.0.166 | 6 / 0 | |
| 2.0.165 | 6 / 0 | |
| 2.0.164 | 6 / 0 | |
| 2.0.163 | 6 / 0 | |
| 2.0.162 | 6 / 0 | |
| 2.0.161 | 6 / 0 | |
| 2.0.160 | 6 / 0 | |
| 2.0.159 | 6 / 0 | |
| 2.0.158 | 6 / 0 | |
| 2.0.157 | 6 / 0 | |
| 2.0.156 | 6 / 0 | |
| 2.0.155 | 6 / 0 | |
| 2.0.154 | 6 / 0 | |
| 2.0.153 | 6 / 0 | |
| 2.0.152 | 6 / 0 | |
| 2.0.151 | 6 / 0 | |
| 2.0.150 | 6 / 0 | |
| 2.0.149 | 6 / 0 | |
| 2.0.148 | 6 / 0 | |
| 2.0.147 | 6 / 0 | |
| 2.0.146 | 6 / 0 | |
| 2.0.145 | 6 / 0 | |
| 2.0.144 | 6 / 0 | |
| 2.0.143 | 6 / 0 | |
| 2.0.142 | 6 / 0 | |
| 2.0.141 | 6 / 0 | |
| 2.0.140 | 6 / 0 | |
| 2.0.139 | 6 / 0 | |
| 2.0.138 | 6 / 0 | |
| 2.0.137 | 6 / 0 | |
| 2.0.136 | 6 / 0 | |
| 2.0.135 | 6 / 0 | |
| 2.0.134 | 6 / 0 | |
| 2.0.133 | 6 / 0 | |
| 2.0.132 | 6 / 0 | |
| 2.0.131 | 6 / 0 | |
| 2.0.130 | 6 / 0 | |
| 2.0.129 | 6 / 0 | |
| 2.0.128 | 6 / 0 | |
| 2.0.127 | 6 / 0 | |
| 2.0.126 | 6 / 0 | |
| 2.0.125 | 6 / 0 | |
| 2.0.124 | 6 / 0 | |
| 2.0.123 | 6 / 0 | |
| 2.0.122 | 6 / 0 | |
| 2.0.121 | 6 / 0 | |
| 2.0.120 | 6 / 0 | |
| 2.0.118 | 6 / 0 | |
| 2.0.117 | 6 / 0 | |
| 2.0.116 | 6 / 0 | |
| 2.0.115 | 6 / 0 | |
| 2.0.114 | 6 / 0 | |
| 2.0.113 | 6 / 0 |
v2.0.214
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.213
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.211
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.202
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.195
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.188
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.186
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.185
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.184
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.178
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.