VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

it-length-prefixed: vulnerability history, versions and safety

it-length-prefixed 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 it-length-prefixed vulnerabilities

Vulert verdict on it-length-prefixed 11.0.1 i

Updated on 23 Oct 2026

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

Package health score 67/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

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

  • Current release 11.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 465 packages i
  • Stars 4 i
  • OpenSSF scorecard 2/10 i
  • Last release 5 months ago i
  • Licence Apache-2.0 OR 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 it-length-prefixed, 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
11.0.1 08 May 2026 none Apache-2.0 OR MIT — Details →
11.0.0 07 May 2026 none Apache-2.0 OR MIT — Details →
10.0.2 07 May 2026 none Apache-2.0 OR MIT — Details →
10.0.1 13 Feb 2025 none Apache-2.0 OR MIT — Details →
10.0.0 03 Feb 2025 none Apache-2.0 OR MIT — Details →
9.1.1 24 Jan 2025 none Apache-2.0 OR MIT — Details →
9.1.0 08 Aug 2024 none Apache-2.0 OR MIT — Details →
9.0.5 07 Aug 2024 none Apache-2.0 OR MIT — Details →
9.0.4 30 Dec 2023 none Apache-2.0 OR MIT — Details →
9.0.3 16 Aug 2023 none Apache-2.0 OR MIT — Details →
9.0.2 16 Aug 2023 none Apache-2.0 OR MIT — Details →
9.0.1 18 Apr 2023 none Apache-2.0 OR MIT — Details →
9.0.0 31 Mar 2023 none Apache-2.0 OR MIT — Details →
8.0.4 22 Dec 2022 none Apache-2.0 OR MIT — Details →
8.0.3 12 Oct 2022 none Apache-2.0 OR MIT — Details →
8.0.2 30 Jul 2022 none Apache-2.0 OR MIT — Details →
8.0.1 28 Jul 2022 none Apache-2.0 OR MIT — Details →
8.0.0 28 Jul 2022 none Apache-2.0 OR MIT — Details →
7.0.1 08 Mar 2022 none Apache-2.0 OR MIT — Details →
7.0.0 16 Feb 2022 none Apache-2.0 OR MIT — Details →
6.0.1 13 Jan 2022 none MIT — Details →
6.0.0 13 Jan 2022 none MIT — Details →
5.0.3 07 Jul 2021 none MIT — Details →
5.0.2 09 Apr 2021 none MIT — Details →
5.0.1 09 Apr 2021 none MIT — Details →
5.0.0 08 Apr 2021 none MIT — Details →
4.0.0 01 Apr 2021 none MIT — Details →
3.1.0 27 Jul 2020 none MIT — Details →
3.0.1 18 Mar 2020 none MIT — Details →
3.0.0 13 Nov 2019 none MIT — Details →
2.0.0 26 Sep 2019 none MIT — Details →
1.1.0 13 Aug 2019 none MIT — Details →
1.0.0 07 May 2019 none MIT — Details →

All 33 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 it-length-prefixed

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 it-length-prefixed

Is it-length-prefixed safe to use?

Vulert has no vulnerabilities on record for it-length-prefixed 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 it-length-prefixed's Vulert package health score?

Vulert scores it-length-prefixed 67/100, which reads as usable, but worth attention. 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 it-length-prefixed affected?

No. 11.0.1, 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 it-length-prefixed should I use?

11.0.1 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 it-length-prefixed have?

0 vulnerabilities are recorded for it-length-prefixed 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 it-length-prefixed vulnerabilities disclosed?

0 vulnerabilities were recorded for it-length-prefixed 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 it-length-prefixed 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 it-length-prefixed for upcoming vulnerabilities?

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