VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@chain-registry/utils: vulnerability history, versions and safety

@chain-registry/utils is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @chain-registry/utils vulnerabilities

Vulert verdict on @chain-registry/utils 2.0.283 i

Updated on 23 Oct 2026

Good news: 2.0.283, the version you would install today, has no known vulnerabilities.

Package health score 85/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 2.0.283 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.0.283 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.0.283 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 6 packages i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @chain-registry/utils, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.0.283 19 Oct 2026 none MIT — Details →
1.51.444 19 Oct 2026 none MIT — Details →
2.0.282 12 Oct 2026 none MIT — Details →
1.51.443 12 Oct 2026 none MIT — Details →
1.51.442 05 Oct 2026 none MIT — Details →
1.51.441 01 Oct 2026 none MIT — Details →
2.0.281 01 Oct 2026 none MIT — Details →
2.0.251 14 Aug 2026 none MIT — Details →
1.51.410 14 Aug 2026 none MIT — Details →
1.51.409 12 Aug 2026 none MIT — Details →
2.0.250 11 Aug 2026 none MIT — Details →
1.51.408 11 Aug 2026 none MIT — Details →
2.0.249 08 Aug 2026 none MIT — Details →
1.51.407 08 Aug 2026 none MIT — Details →
2.0.248 07 Aug 2026 none MIT — Details →
1.51.406 07 Aug 2026 none MIT — Details →
2.0.247 06 Aug 2026 none MIT — Details →
1.51.405 06 Aug 2026 none MIT — Details →
2.0.246 05 Aug 2026 none MIT — Details →
1.51.404 05 Aug 2026 none MIT — Details →
2.0.245 01 Aug 2026 none MIT — Details →
1.51.403 01 Aug 2026 none MIT — Details →
2.0.244 31 Jul 2026 none MIT — Details →
1.51.402 31 Jul 2026 none MIT — Details →
1.51.401 26 Jul 2026 none MIT — Details →
2.0.243 25 Jul 2026 none MIT — Details →
1.51.400 25 Jul 2026 none MIT — Details →
2.0.242 24 Jul 2026 none MIT — Details →
1.51.399 24 Jul 2026 none MIT — Details →
2.0.241 23 Jul 2026 none MIT — Details →
1.51.398 23 Jul 2026 none MIT — Details →
2.0.240 22 Jul 2026 none MIT — Details →
1.51.397 22 Jul 2026 none MIT — Details →
2.0.239 21 Jul 2026 none MIT — Details →
1.51.396 21 Jul 2026 none MIT — Details →
2.0.238 18 Jul 2026 none MIT — Details →
1.51.395 18 Jul 2026 none MIT — Details →
2.0.237 17 Jul 2026 none MIT — Details →
1.51.394 17 Jul 2026 none MIT — Details →
2.0.236 16 Jul 2026 none MIT — Details →
1.51.393 16 Jul 2026 none MIT — Details →
2.0.235 15 Jul 2026 none MIT — Details →
1.51.392 15 Jul 2026 none MIT — Details →
2.0.234 14 Jul 2026 none MIT — Details →
1.51.391 14 Jul 2026 none MIT — Details →
2.0.233 11 Jul 2026 none MIT — Details →
1.51.390 11 Jul 2026 none MIT — Details →
2.0.232 10 Jul 2026 none MIT — Details →
1.51.389 10 Jul 2026 none MIT — Details →
2.0.231 09 Jul 2026 none MIT — Details →
1.51.388 09 Jul 2026 none MIT — Details →
2.0.230 08 Jul 2026 none MIT — Details →
2.0.229 07 Jul 2026 none MIT — Details →
1.51.387 07 Jul 2026 none MIT — Details →
1.51.386 04 Jul 2026 none MIT — Details →
2.0.228 03 Jul 2026 none MIT — Details →
1.51.385 03 Jul 2026 none MIT — Details →
2.0.227 02 Jul 2026 none MIT — Details →
1.51.384 02 Jul 2026 none MIT — Details →
2.0.226 01 Jul 2026 none MIT — Details →
1.51.383 01 Jul 2026 none MIT — Details →
2.0.225 30 Jun 2026 none MIT — Details →
1.51.382 30 Jun 2026 none MIT — Details →
2.0.224 24 Jun 2026 none MIT — Details →
1.51.381 24 Jun 2026 none MIT — Details →
2.0.223 23 Jun 2026 none MIT — Details →
1.51.380 23 Jun 2026 none MIT — Details →
2.0.222 20 Jun 2026 none MIT — Details →
1.51.379 20 Jun 2026 none MIT — Details →
2.0.221 19 Jun 2026 none MIT — Details →
1.51.378 19 Jun 2026 none MIT — Details →
2.0.220 18 Jun 2026 none MIT — Details →
1.51.377 18 Jun 2026 none MIT — Details →
2.0.219 17 Jun 2026 none MIT — Details →
1.51.376 17 Jun 2026 none MIT — Details →
2.0.218 16 Jun 2026 none MIT — Details →
1.51.375 16 Jun 2026 none MIT — Details →
2.0.217 13 Jun 2026 none MIT — Details →
1.51.374 13 Jun 2026 none MIT — Details →
2.0.216 12 Jun 2026 none MIT — Details →
1.51.373 12 Jun 2026 none MIT — Details →
2.0.215 11 Jun 2026 none MIT — Details →
1.51.372 11 Jun 2026 none MIT — Details →
2.0.214 09 Jun 2026 none MIT — Details →
1.51.371 09 Jun 2026 none MIT — Details →
2.0.213 06 Jun 2026 none MIT — Details →
1.51.370 06 Jun 2026 none MIT — Details →
2.0.212 05 Jun 2026 none MIT — Details →
1.51.369 05 Jun 2026 none MIT — Details →
2.0.211 04 Jun 2026 none MIT — Details →
1.51.368 04 Jun 2026 none MIT — Details →
2.0.210 03 Jun 2026 none MIT — Details →
1.51.367 03 Jun 2026 none MIT — Details →
2.0.209 02 Jun 2026 none MIT — Details →
1.51.366 02 Jun 2026 none MIT — Details →
2.0.208 30 May 2026 none MIT — Details →
1.51.365 30 May 2026 none MIT — Details →
2.0.207 26 May 2026 none MIT — Details →
1.51.364 26 May 2026 none MIT — Details →
2.0.206 22 May 2026 none MIT — Details →
1.51.363 22 May 2026 none — — Details →
2.0.205 21 May 2026 none — — Details →
1.51.362 21 May 2026 none — — Details →
2.0.204 20 May 2026 none — — Details →
1.51.361 20 May 2026 none — — Details →
2.0.203 19 May 2026 none — — Details →
1.51.360 19 May 2026 none — — Details →
2.0.202 16 May 2026 none — — Details →
1.51.359 16 May 2026 none — — Details →
2.0.201 15 May 2026 none — — Details →
1.51.358 15 May 2026 none — — Details →
2.0.200 14 May 2026 none — — Details →
1.51.357 14 May 2026 none — — Details →
1.51.356 13 May 2026 none — — Details →
2.0.199 12 May 2026 none — — Details →
1.51.355 12 May 2026 none — — Details →
1.51.354 09 May 2026 none — — Details →
2.0.198 08 May 2026 none — — Details →
1.51.353 08 May 2026 none — — Details →
2.0.197 07 May 2026 none — — Details →

The newest 120 of 912 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for @chain-registry/utils

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @chain-registry/utils

Is @chain-registry/utils safe to use?

Vulert has no vulnerabilities on record for @chain-registry/utils in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is @chain-registry/utils's Vulert package health score?

Vulert scores @chain-registry/utils 85/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @chain-registry/utils affected?

No. 2.0.283, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @chain-registry/utils have?

0 vulnerabilities are recorded for @chain-registry/utils in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @chain-registry/utils vulnerabilities disclosed?

0 vulnerabilities were recorded for @chain-registry/utils in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @chain-registry/utils are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @chain-registry/utils for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @chain-registry/utils version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.