VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

slug: vulnerability history, versions and safety

slug is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 20 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 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 slug vulnerabilities

Vulert verdict on slug 12.0.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 12.0.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Jul 2018 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 23 packages i
  • Stars 414 i
  • OpenSSF scorecard 4/10 i
  • Last release 3 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 slug, 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
12.0.1 21 Jul 2026 none MIT — Details →
12.0.0 19 Jul 2026 none MIT — Details →
11.0.1 13 Oct 2025 none MIT — Details →
11.0.0 22 May 2025 none MIT — Details →
11.0.0-beta.1 19 Oct 2024 none MIT — Details →
10.0.0 17 Oct 2024 none MIT — Details →
9.1.0 24 May 2024 none MIT — Details →
9.0.0 07 Mar 2024 none MIT — Details →
8.2.3 18 Jul 2023 none MIT — Details →
8.2.2 02 Oct 2022 none MIT — Details →
8.2.1 02 Oct 2022 none MIT — Details →
8.2.0 02 Oct 2022 none MIT — Details →
8.1.0 02 Oct 2022 none MIT — Details →
9.0.0-beta.1 31 Aug 2022 none MIT — Details →
8.0.0 31 Aug 2022 none MIT — Details →
7.0.0 31 Aug 2022 none MIT — Details →
6.1.0 31 Aug 2022 none MIT — Details →
7.0.0-beta.1 18 Aug 2022 none MIT — Details →
6.0.0 16 Aug 2022 none MIT — Details →
6.0.0-beta.4 20 Apr 2022 none MIT — Details →
6.0.0-beta.3 20 Apr 2022 none MIT — Details →
6.0.0-beta.2 20 Apr 2022 none MIT — Details →
6.0.0-beta.1 19 Apr 2022 none MIT — Details →
5.3.0 04 Mar 2022 none MIT — Details →
5.2.0 27 Dec 2021 none MIT — Details →
5.1.1 13 Dec 2021 none MIT — Details →
5.1.0 15 Jun 2021 none MIT — Details →
5.0.1 09 May 2021 none MIT — Details →
5.0.0 03 May 2021 none MIT — Details →
4.1.0 03 May 2021 none MIT — Details →
4.0.4 16 Apr 2021 none MIT — Details →
4.0.3 24 Feb 2021 none MIT — Details →
4.0.2 30 Oct 2020 none MIT — Details →
4.0.1 22 Oct 2020 none MIT — Details →
4.0.0 21 Oct 2020 none MIT — Details →
3.5.2 20 Oct 2020 none MIT — Details →
3.5.1 13 Oct 2020 none MIT — Details →
3.5.0 11 Oct 2020 none MIT — Details →
3.4.0 11 Oct 2020 none MIT — Details →
3.3.6 11 Oct 2020 none MIT — Details →
3.3.5 29 Sep 2020 none MIT — Details →
3.3.4 01 Aug 2020 none MIT — Details →
3.3.3 01 Aug 2020 none MIT — Details →
3.3.2 17 Jul 2020 none MIT — Details →
3.3.1 16 Jul 2020 none MIT — Details →
3.3.0 30 May 2020 none MIT — Details →
3.2.0 28 May 2020 none MIT — Details →
3.1.0 28 May 2020 none MIT — Details →
3.0.1 20 May 2020 none MIT — Details →
3.0.0 20 May 2020 none MIT — Details →
2.1.1 25 Jan 2020 none MIT — Details →
2.1.0 31 Dec 2019 none MIT — Details →
2.0.0 24 Dec 2019 none MIT — Details →
1.1.0 30 Mar 2019 none MIT — Details →
1.0.0 21 Feb 2019 none MIT — Details →
0.9.4 21 Feb 2019 none MIT — Details →
0.9.3 10 Dec 2018 none MIT — Details →
0.9.2 25 Oct 2018 none MIT — Details →
0.9.1 18 Apr 2015 M1 MIT Yes Details →
0.9.0 18 Apr 2015 M1 MIT Yes Details →
0.8.0 09 Oct 2014 M1 MIT Yes Details →
0.7.1 25 Sep 2014 M1 MIT Yes Details →
0.7.0 22 Sep 2014 M1 MIT Yes Details →
0.6.0 14 Sep 2014 M1 MIT Yes Details →
0.5.0 30 Apr 2014 M1 MIT Yes Details →
0.4.2 20 Feb 2014 M1 MIT Yes Details →
0.4.1 19 Feb 2014 M1 MIT Yes Details →
0.4.0 10 Nov 2013 M1 MIT Yes Details →
0.3.4 31 Oct 2013 M1 MIT Yes Details →
0.3.3 26 Jun 2013 M1 MIT Yes Details →
0.3.2 22 Jun 2013 M1 MIT Yes Details →
0.3.1 22 Jun 2013 M1 MIT Yes Details →
0.3.0 22 Jun 2013 M1 MIT Yes Details →
0.2.2 13 Jan 2012 M1 MIT Yes Details →
0.2.1 06 Jan 2012 M1 MIT Yes Details →
0.2.0 05 Jan 2012 M1 MIT Yes Details →
0.1.1 29 Nov 2011 M1 MIT Yes Details →
0.1.0 19 Sep 2011 M1 MIT Yes Details →

All 78 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 slug

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16117: Regular Expression Denial of Service in slug N/A medium 0.9.2 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 slug

Is slug safe to use?

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

Vulert scores slug 76/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 slug affected?

No. 12.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 slug should I use?

12.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 slug have?

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

0 vulnerabilities were recorded for slug 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 slug 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 slug for upcoming vulnerabilities?

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