VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

content: vulnerability history, versions and safety

content is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 11 releases, first recorded in Jul 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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 content vulnerabilities

Vulert verdict on content 4.0.6 i

Updated on 23 Oct 2026

Good news: 4.0.6, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 44/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Niche
  • Community Inactive

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release 4.0.6 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Jul 2018 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 801 packages i
  • Stars 7 i
  • OpenSSF scorecard 3/10 i
  • Last release 95 months ago i
  • Licence non-standard 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 content, 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
3.1.2 06 Jan 2024 none non-standard — Details →
4.0.6 03 Nov 2018 none BSD-3-Clause — Details →
4.0.5 31 Mar 2018 none BSD-3-Clause — Details →
3.0.7 01 Mar 2018 none BSD-3-Clause — Details →
4.0.4 01 Mar 2018 none BSD-3-Clause — Details →
4.0.3 03 Nov 2017 none BSD-3-Clause — Details →
4.0.2 03 Nov 2017 none BSD-3-Clause — Details →
4.0.1 26 Sep 2017 none BSD-3-Clause — Details →
4.0.0 26 Sep 2017 none BSD-3-Clause — Details →
3.0.6 12 Sep 2017 H1 BSD-3-Clause Yes Details →
3.0.5 20 Jul 2017 H1 BSD-3-Clause Yes Details →
3.0.4 28 May 2017 H1 BSD-3-Clause Yes Details →
3.0.3 26 Oct 2016 H1 BSD-3-Clause Yes Details →
3.0.2 28 Jul 2016 H1 BSD-3-Clause Yes Details →
3.0.1 07 May 2016 H1 BSD-3-Clause Yes Details →
3.0.0 03 Nov 2015 H1 BSD-3-Clause Yes Details →
2.0.0 22 Oct 2015 H1 BSD-3-Clause Yes Details →
1.0.2 24 Jun 2015 H1 BSD-3-Clause Yes Details →
1.0.1 02 Oct 2014 H1 BSD-3-Clause Yes Details →
1.0.0 02 Oct 2014 H1 BSD-3-Clause Yes Details →

All 20 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for content

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16111: Regular Expression Denial of Service in content 7.5 high 3.0.7 24 Jul 2018

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 content

Is content safe to use?

Vulert records 1 vulnerabilities for content in npm: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is content's Vulert package health score?

Vulert scores content 44/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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of content affected?

No. 4.0.6, 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 content should I use?

4.0.6 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 content have?

1 vulnerability is recorded for content in the npm ecosystem: 0 critical, 1 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 content vulnerabilities disclosed?

0 vulnerabilities were recorded for content in the last 12 months, and the oldest entry in this database dates to 24 Jul 2018. 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 content 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 content for upcoming vulnerabilities?

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