VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ssri: vulnerability history, versions and safety

ssri is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 23 releases, from Mar 2018 to Mar 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
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 ssri vulnerabilities

Vulert verdict on ssri 14.0.0 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 14.0.0 — unaffected i
  • Vulnerabilities on record 2 over 3 years · 0 in the last year i
  • Latest disclosure 19 Mar 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 576 packages i
  • Stars 59 i
  • OpenSSF scorecard 4/10 i
  • Last release 5 months ago i
  • Licence ISC i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 ssri, 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
14.0.0 08 May 2026 none ISC — Details →
13.0.1 09 Feb 2026 none ISC — Details →
13.0.0 22 Oct 2025 none ISC — Details →
12.0.0 25 Sep 2024 none ISC — Details →
11.0.0 03 Sep 2024 none ISC — Details →
10.0.6 04 May 2024 none ISC — Details →
10.0.5 14 Aug 2023 none ISC — Details →
10.0.4 26 Apr 2023 none ISC — Details →
10.0.3 11 Apr 2023 none ISC — Details →
10.0.2 04 Apr 2023 none ISC — Details →
10.0.1 07 Dec 2022 none ISC — Details →
10.0.0 14 Oct 2022 none ISC — Details →
9.0.1 19 May 2022 none ISC — Details →
9.0.0 05 Apr 2022 none ISC — Details →
7.1.1 17 May 2021 none ISC — Details →
6.0.2 07 Apr 2021 none ISC — Details →
8.0.1 27 Jan 2021 none ISC — Details →
8.0.0 18 Feb 2020 none ISC — Details →
7.1.0 24 Oct 2019 none ISC — Details →
7.0.1 30 Sep 2019 none ISC — Details →
7.0.0 18 Sep 2019 none ISC — Details →
6.0.1 27 Aug 2018 H1 ISC Yes Details →
6.0.0 09 Apr 2018 H1 ISC Yes Details →
5.3.0 13 Mar 2018 H1 ISC Yes Details →
5.2.4 16 Feb 2018 H1 ISC Yes Details →
5.2.3 16 Feb 2018 H1 ISC Yes Details →
5.2.2 14 Feb 2018 H1 ISC Yes Details →
5.2.1 07 Feb 2018 M1 ISC Yes Details →
5.1.0 18 Jan 2018 M1 ISC Yes Details →
5.0.0 23 Oct 2017 M1 ISC Yes Details →
4.1.6 07 Jun 2017 M1 CC0-1.0 Yes Details →
4.1.5 05 Jun 2017 M1 CC0-1.0 Yes Details →
4.1.4 31 May 2017 M1 CC0-1.0 Yes Details →
4.1.3 24 May 2017 M1 CC0-1.0 Yes Details →
4.1.2 18 Apr 2017 M1 CC0-1.0 Yes Details →
4.1.1 12 Apr 2017 M1 CC0-1.0 Yes Details →
4.1.0 07 Apr 2017 M1 CC0-1.0 Yes Details →
4.0.0 03 Apr 2017 M1 CC0-1.0 Yes Details →
3.0.2 03 Apr 2017 M1 CC0-1.0 Yes Details →
3.0.1 03 Apr 2017 M1 CC0-1.0 Yes Details →
3.0.0 03 Apr 2017 M1 CC0-1.0 Yes Details →
2.0.0 24 Mar 2017 M1 CC0-1.0 Yes Details →
1.0.0 23 Mar 2017 M1 CC0-1.0 Yes Details →
0.0.0 23 Mar 2017 M1 CC0-1.0 Yes Details →

All 44 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
  • 2021 1

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

03 Vulnerabilities

Recorded vulnerabilities for ssri

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2021-27290: Regular Expression Denial of Service (ReDoS) in ssri 7.5 high 6.0.2 19 Mar 2021
CVE-2018-7651: Regular Expression Denial of Service in ssri 5.9 medium 5.2.2 07 Mar 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 ssri

Is ssri safe to use?

Vulert records 2 vulnerabilities for ssri in npm: 0 critical, 1 high, 1 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 ssri's Vulert package health score?

Vulert scores ssri 73/100, which reads as in good shape. 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 ssri affected?

No. 14.0.0, 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 ssri should I use?

14.0.0 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 ssri have?

2 vulnerabilities are recorded for ssri in the npm ecosystem: 0 critical, 1 high, 1 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 ssri vulnerabilities disclosed?

0 vulnerabilities were recorded for ssri in the last 12 months, and the oldest entry in this database dates to 07 Mar 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 ssri 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 ssri for upcoming vulnerabilities?

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