← Home

@chain-registry/assets

npm Repository Homepage

Chain Registry Asset Lists

100
Versions
SEE LICENSE IN LICENSE
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

pyramationluca608zetazz

Keywords

chain-registryweb3cosmoscosmos-sdkinterchaintokens

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 of 950)

Version Deps Published
1.70.251 1 / 2
1.70.250 1 / 2
1.70.249 1 / 2
1.70.248 1 / 2
1.70.247 1 / 2
1.70.246 1 / 2
1.70.245 1 / 2
1.70.244 1 / 2
1.70.243 1 / 2
1.70.242 1 / 2
1.70.241 1 / 2
1.70.240 1 / 2
1.70.239 1 / 2
1.70.238 1 / 2
1.70.237 1 / 2
1.70.236 1 / 2
1.70.235 1 / 2
1.70.234 1 / 2
1.70.233 1 / 2
1.70.232 1 / 2
1.70.231 1 / 2
1.70.230 1 / 2
1.70.229 1 / 2
1.70.228 1 / 2
1.70.227 1 / 2
1.70.226 1 / 2
1.70.225 1 / 2
1.70.224 1 / 2
1.70.223 1 / 2
1.70.222 1 / 2
1.70.221 1 / 2
1.70.220 1 / 2
1.70.219 1 / 2
1.70.218 1 / 2
1.70.217 1 / 2
1.70.216 1 / 2
1.70.215 1 / 2
1.70.214 1 / 2
1.70.213 1 / 2
1.70.212 1 / 2
1.70.211 1 / 2
1.70.210 1 / 2
1.70.209 1 / 2
1.70.208 1 / 2
1.70.207 1 / 2
1.70.206 1 / 2
1.70.205 1 / 2
1.70.204 1 / 2
1.70.203 1 / 2
1.70.202 1 / 2
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
1.70.193 1 / 2
1.70.192 1 / 2
1.70.191 1 / 2
1.70.190 1 / 2
1.70.189 1 / 2
1.70.188 1 / 2
1.70.187 1 / 2
1.70.186 1 / 2
1.70.185 1 / 2
1.70.184 1 / 2
1.70.183 1 / 2
1.70.182 1 / 2
1.70.181 1 / 2
1.70.179 1 / 2
1.70.178 1 / 2
1.70.177 1 / 2
1.70.176 1 / 2
1.70.175 1 / 2
1.70.174 1 / 2
1.70.173 1 / 2
1.70.172 1 / 2
1.70.171 1 / 2
1.70.170 1 / 2
1.70.169 1 / 2
1.70.168 1 / 2
1.70.167 1 / 2
1.70.166 1 / 2
1.70.165 1 / 2
1.70.164 1 / 2
1.70.163 1 / 2
1.70.162 1 / 2
1.70.161 1 / 2
1.70.160 1 / 2
1.70.159 1 / 2
1.70.158 1 / 2
1.70.157 1 / 2
1.70.156 1 / 2
1.70.155 1 / 2
1.70.154 1 / 2
1.70.153 1 / 2
1.70.152 1 / 2
1.70.151 1 / 2
Showing 100 of 950 Next page →

v1.70.193

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.192

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.191

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.190

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.189

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.188

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.187

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.186

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.185

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.184

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.183

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.182

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.181

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.179

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.178

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.177

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.176

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.175

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.174

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.173

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.172

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.171

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.170

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.169

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.168

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.167

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.166

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.165

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.164

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.163

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.162

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.161

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.160

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.159

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.158

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.157

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.156

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.155

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.154

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.153

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.152

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.70.151

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.