VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

subtext: vulnerability history, versions and safety

subtext is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 40 releases, first recorded in Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H3
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 subtext vulnerabilities

Vulert verdict on subtext 6.0.12 i

Updated on 23 Oct 2026

Careful: 6.0.12 has 3 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

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

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.0.12 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 03 Sep 2020 i
  • Highest CVSS n/a i
  • With no published fix 3 i
  • Depended on by 794 packages i
  • Stars 24 i
  • OpenSSF scorecard 3/10 i
  • Last release 92 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 subtext, 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
5.1.3 06 Jan 2024 H3 non-standard No Details →
6.0.12 31 Jan 2019 H3 BSD-3-Clause No Details →
5.0.1 31 Jan 2019 H3 BSD-3-Clause No Details →
6.0.11 03 Nov 2018 H3 BSD-3-Clause No Details →
6.0.10 02 Nov 2018 H3 BSD-3-Clause No Details →
6.0.9 01 Nov 2018 H3 BSD-3-Clause No Details →
6.0.8 31 Oct 2018 H3 BSD-3-Clause No Details →
6.0.7 03 Nov 2017 H3 BSD-3-Clause No Details →
6.0.6 03 Nov 2017 H3 BSD-3-Clause No Details →
6.0.5 22 Oct 2017 H3 BSD-3-Clause No Details →
6.0.4 19 Oct 2017 H3 BSD-3-Clause No Details →
6.0.3 28 Sep 2017 H3 BSD-3-Clause No Details →
6.0.1 26 Sep 2017 H3 BSD-3-Clause No Details →
6.0.0 18 Sep 2017 H3 BSD-3-Clause No Details →
5.0.0 30 Jun 2017 H3 BSD-3-Clause No Details →
4.4.1 28 May 2017 H3 BSD-3-Clause No Details →
4.4.0 21 Mar 2017 H3 BSD-3-Clause No Details →
4.3.0 19 Oct 2016 H3 BSD-3-Clause No Details →
4.2.2 27 Sep 2016 H3 BSD-3-Clause No Details →
4.2.1 26 Aug 2016 H3 BSD-3-Clause No Details →
4.2.0 26 Aug 2016 H3 BSD-3-Clause No Details →
4.1.0 22 Aug 2016 H3 BSD-3-Clause No Details →
4.0.5 28 Jul 2016 H2 BSD-3-Clause No Details →
4.0.4 21 May 2016 H2 BSD-3-Clause No Details →
4.0.3 11 May 2016 H2 BSD-3-Clause No Details →
4.0.2 08 May 2016 H2 BSD-3-Clause No Details →
4.0.1 06 Apr 2016 H2 BSD-3-Clause No Details →
4.0.0 22 Dec 2015 H2 BSD-3-Clause No Details →
3.0.2 14 Nov 2015 H2 BSD-3-Clause No Details →
3.0.1 14 Nov 2015 H2 BSD-3-Clause No Details →
3.0.0 03 Nov 2015 H2 BSD-3-Clause No Details →
2.0.2 20 Oct 2015 H2 BSD-3-Clause No Details →
2.0.1 30 Sep 2015 H2 BSD-3-Clause No Details →
2.0.0 11 Aug 2015 H2 BSD-3-Clause No Details →
1.1.1 03 Jul 2015 H2 BSD-3-Clause No Details →
1.1.0 01 Jul 2015 H2 BSD-3-Clause No Details →
1.0.2 07 Nov 2014 H2 BSD-3-Clause No Details →
1.0.1 02 Oct 2014 H2 BSD-3-Clause No Details →
1.0.0 02 Oct 2014 H2 BSD-3-Clause No Details →
0.0.0 29 Sep 2014 H2 BSD-3-Clause No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 3

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

03 Vulnerabilities

Recorded vulnerabilities for subtext

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service in subtext N/A high No fix published 03 Sep 2020
Denial of Service in subtext N/A high No fix published 03 Sep 2020
Prototype Pollution in subtext N/A high No fix published 03 Sep 2020

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 subtext

Is subtext safe to use?

Vulert records 3 vulnerabilities for subtext in npm: 0 critical, 3 high, 0 medium and 0 low. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is subtext's Vulert package health score?

Vulert scores subtext 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 subtext affected?

Yes. 6.0.12, the version you would install today, has 3 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of subtext should I use?

6.0.12 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 subtext have?

3 vulnerabilities are recorded for subtext in the npm ecosystem: 0 critical, 3 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 subtext vulnerabilities disclosed?

0 vulnerabilities were recorded for subtext in the last 12 months, and the oldest entry in this database dates to 03 Sep 2020. 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 subtext 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 subtext for upcoming vulnerabilities?

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