VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

code-error-fragment: vulnerability history, versions and safety

code-error-fragment 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 code-error-fragment vulnerabilities

Vulert verdict on code-error-fragment 0.0.230 i

Updated on 23 Oct 2026

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

Package health score 49/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Inactive

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

  • Current release 0.0.230 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,042 packages i
  • Stars 2 i
  • OpenSSF scorecard 1/10 i
  • Last release 107 months ago 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 code-error-fragment, 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
0.0.230 25 Oct 2017 none MIT — Details →
0.0.229 25 Oct 2017 none MIT — Details →
0.0.228 24 Oct 2017 none MIT — Details →
0.0.227 24 Oct 2017 none MIT — Details →
0.0.226 22 Oct 2017 none MIT — Details →
0.0.223 19 Oct 2017 none MIT — Details →
0.0.222 19 Oct 2017 none MIT — Details →
0.0.221 19 Oct 2017 none MIT — Details →
0.0.220 19 Oct 2017 none MIT — Details →
0.0.219 19 Oct 2017 none MIT — Details →
0.0.218 19 Oct 2017 none MIT — Details →
0.0.217 19 Oct 2017 none MIT — Details →
0.0.216 19 Oct 2017 none MIT — Details →
0.0.215 18 Oct 2017 none MIT — Details →
0.0.214 18 Oct 2017 none MIT — Details →
0.0.213 18 Oct 2017 none MIT — Details →
0.0.212 18 Oct 2017 none MIT — Details →
0.0.211 18 Oct 2017 none MIT — Details →
0.0.21 18 Oct 2017 none MIT — Details →
0.0.2 18 Oct 2017 none MIT — Details →
0.0.1 13 Oct 2017 none MIT — Details →

All 21 versions Vulert tracks for this package. 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 code-error-fragment

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 code-error-fragment

Is code-error-fragment safe to use?

Vulert has no vulnerabilities on record for code-error-fragment 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 code-error-fragment's Vulert package health score?

Vulert scores code-error-fragment 49/100, which reads as risky. 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 code-error-fragment affected?

No. 0.0.230, 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.

Which version of code-error-fragment should I use?

0.0.230 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does code-error-fragment have?

0 vulnerabilities are recorded for code-error-fragment 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 code-error-fragment vulnerabilities disclosed?

0 vulnerabilities were recorded for code-error-fragment 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 code-error-fragment 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 code-error-fragment for upcoming vulnerabilities?

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