@chain-registry/assets
Chain Registry Asset Lists
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-tlds | AI (semgrep): Package is a blockchain chain registry containing static metadata (website URLs, social links) for crypto projects. .xyz and similar TLDs are common in web3; these are data strings, not network calls or C2 infrastructure. | ai | |
| phantom-deps | phantom-dep:@chain-registry/types | AI (phantom-deps): @chain-registry/types is a types-only peer package from the same org; not being directly imported in JS is expected for a TypeScript types dependency. | ai |
Versions (showing 8 of 417)
| Version | Deps | Published |
|---|---|---|
| 1.70.201 | 1 / 2 | |
| 1.70.200 | 1 / 2 | |
| 1.70.199 | 1 / 2 | |
| 1.70.198 | 1 / 2 | |
| 1.70.197 | 1 / 2 | |
| 1.70.196 | 1 / 2 | |
| 1.70.195 | 1 / 2 | |
| 1.70.194 | 1 / 2 |
v1.70.201
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.