VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

docsify: vulnerability history, versions and safety

docsify is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 111 releases, from Mar 2021 to May 2022. 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 M3
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 docsify vulnerabilities

Vulert verdict on docsify 5.0.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 5.0.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 5 packages i
  • Stars 31,554 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 docsify, 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.0.0 23 Jul 2026 none MIT — Details →
5.0.0-rc.4 11 Mar 2026 none MIT — Details →
5.0.0-rc.3 05 Sep 2025 none MIT — Details →
5.0.0-rc.2 05 Sep 2025 none MIT — Details →
5.0.0-rc.1 27 May 2025 none MIT — Details →
4.13.1 24 Jun 2023 none MIT — Details →
4.13.0 26 Oct 2022 none MIT — Details →
4.12.4 26 Oct 2022 none MIT — Details →
4.12.2 06 Jan 2022 none MIT — Details →
4.12.1 07 Mar 2021 M1 MIT Yes Details →
4.12.0 08 Feb 2021 M1 MIT Yes Details →
4.11.6 22 Aug 2020 M2 MIT Yes Details →
4.11.5 21 Aug 2020 M2 MIT Yes Details →
4.11.4 18 Jun 2020 M2 MIT Yes Details →
4.11.3 24 Mar 2020 M3 MIT Yes Details →
4.11.2 09 Mar 2020 M3 MIT Yes Details →
4.11.1 09 Mar 2020 M3 MIT Yes Details →
4.11.0 09 Mar 2020 M3 MIT Yes Details →
4.10.2 16 Dec 2019 M3 MIT Yes Details →
4.10.0 16 Dec 2019 M3 MIT Yes Details →
4.9.4 05 May 2019 M3 MIT Yes Details →
4.9.2 21 Apr 2019 M3 MIT Yes Details →
4.9.1 21 Feb 2019 M3 MIT Yes Details →
4.9.0 19 Feb 2019 M3 MIT Yes Details →
4.8.6 12 Nov 2018 M3 MIT Yes Details →
4.8.5 02 Nov 2018 M3 MIT Yes Details →
4.8.4 01 Nov 2018 M3 MIT Yes Details →
4.8.3 01 Nov 2018 M3 MIT Yes Details →
4.8.2 01 Nov 2018 M3 MIT Yes Details →
4.8.1 31 Oct 2018 M3 MIT Yes Details →
4.8.0 31 Oct 2018 M3 MIT Yes Details →
4.7.1 30 Aug 2018 M3 MIT Yes Details →
4.7.0 29 Jun 2018 M3 MIT Yes Details →
4.6.10 25 Mar 2018 M3 MIT Yes Details →
4.6.9 10 Mar 2018 M3 MIT Yes Details →
4.6.8 06 Mar 2018 M3 MIT Yes Details →
4.6.7 03 Mar 2018 M3 MIT Yes Details →
4.6.6 03 Mar 2018 M3 MIT Yes Details →
4.6.5 03 Mar 2018 M3 MIT Yes Details →
4.6.4 01 Mar 2018 M3 MIT Yes Details →
4.6.3 15 Feb 2018 M3 MIT Yes Details →
4.6.2 14 Feb 2018 M3 MIT Yes Details →
4.6.1 12 Feb 2018 M3 MIT Yes Details →
4.6.0 11 Feb 2018 M3 MIT Yes Details →
4.5.9 07 Feb 2018 M3 MIT Yes Details →
4.5.7 29 Dec 2017 M3 MIT Yes Details →
4.5.6 14 Dec 2017 M3 MIT Yes Details →
4.5.5 30 Nov 2017 M3 MIT Yes Details →
4.5.4 29 Nov 2017 M3 MIT Yes Details →
4.5.3 11 Nov 2017 M3 MIT Yes Details →
4.5.2 09 Nov 2017 M3 MIT Yes Details →
4.5.1 07 Nov 2017 M3 MIT Yes Details →
4.5.0 04 Nov 2017 M3 MIT Yes Details →
4.4.1 31 Oct 2017 M3 MIT Yes Details →
4.4.0 30 Oct 2017 M3 MIT Yes Details →
4.3.15 20 Oct 2017 M3 MIT Yes Details →
4.3.14 20 Oct 2017 M3 MIT Yes Details →
4.3.13 17 Oct 2017 M3 MIT Yes Details →
4.3.12 15 Oct 2017 M3 MIT Yes Details →
4.3.11 15 Oct 2017 M3 MIT Yes Details →
4.3.10 12 Oct 2017 M3 MIT Yes Details →
4.3.9 11 Oct 2017 M3 MIT Yes Details →
4.3.8 07 Oct 2017 M3 MIT Yes Details →
4.3.7 02 Oct 2017 M3 MIT Yes Details →
4.3.6 21 Sep 2017 M3 MIT Yes Details →
4.3.5 20 Sep 2017 M3 MIT Yes Details →
4.3.4 07 Sep 2017 M3 MIT Yes Details →
4.3.3 06 Sep 2017 M3 MIT Yes Details →
4.3.2 01 Sep 2017 M3 MIT Yes Details →
4.3.1 30 Aug 2017 M3 MIT Yes Details →
4.3.0 17 Aug 2017 M3 MIT Yes Details →
4.2.9 15 Aug 2017 M3 MIT Yes Details →
4.2.8 10 Aug 2017 M3 MIT Yes Details →
4.2.7 05 Aug 2017 M3 MIT Yes Details →
4.2.6 27 Jul 2017 M3 MIT Yes Details →
4.2.4 26 Jul 2017 M3 MIT Yes Details →
4.2.3 26 Jul 2017 M3 MIT Yes Details →
4.2.2 24 Jul 2017 M3 MIT Yes Details →
4.2.1 19 Jul 2017 M3 MIT Yes Details →
4.2.0 10 Jul 2017 M3 MIT Yes Details →
4.1.14 24 Jun 2017 M3 MIT Yes Details →
4.1.13 11 Jun 2017 M3 MIT Yes Details →
4.1.12 03 Jun 2017 M3 MIT Yes Details →
4.1.11 02 Jun 2017 M3 MIT Yes Details →
4.1.10 02 Jun 2017 M3 MIT Yes Details →
4.1.9 31 May 2017 M3 MIT Yes Details →
4.1.8 31 May 2017 M3 MIT Yes Details →
4.1.7 30 May 2017 M3 MIT Yes Details →
4.1.6 30 May 2017 M3 MIT Yes Details →
4.1.5 30 May 2017 M3 MIT Yes Details →
4.1.4 30 May 2017 M3 MIT Yes Details →
4.1.3 30 May 2017 M3 MIT Yes Details →
4.1.2 30 May 2017 M3 MIT Yes Details →
4.1.1 30 May 2017 M3 MIT Yes Details →
4.1.0 30 May 2017 M3 MIT Yes Details →
4.0.2 30 May 2017 M3 MIT Yes Details →
4.0.1 29 May 2017 M3 MIT Yes Details →
4.0.0 29 May 2017 M3 MIT Yes Details →
3.7.3 22 May 2017 M3 MIT Yes Details →
3.7.2 19 May 2017 M3 MIT Yes Details →
3.7.1 19 May 2017 M3 — Yes Details →
3.7.0 16 May 2017 M3 — Yes Details →
3.6.6 06 May 2017 M3 — Yes Details →
3.6.5 28 Apr 2017 M3 — Yes Details →
3.6.4 28 Apr 2017 M3 — Yes Details →
3.6.3 25 Apr 2017 M3 — Yes Details →
3.6.2 12 Apr 2017 M3 — Yes Details →
3.6.1 09 Apr 2017 M3 — Yes Details →
3.6.0 09 Apr 2017 M3 — Yes Details →
3.5.2 05 Apr 2017 M3 — Yes Details →
3.5.1 25 Mar 2017 M3 — Yes Details →
3.5.0 25 Mar 2017 M3 — Yes Details →
3.4.4 17 Mar 2017 M3 — Yes Details →
3.4.3 16 Mar 2017 M3 — Yes Details →
3.4.2 11 Mar 2017 M3 — Yes Details →
3.4.1 10 Mar 2017 M3 — Yes Details →
3.4.0 09 Mar 2017 M3 — Yes Details →
3.3.0 07 Mar 2017 M3 — Yes Details →
3.2.0 28 Feb 2017 M3 — Yes Details →
3.1.2 27 Feb 2017 M3 — Yes Details →

The newest 120 of 198 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2022 1

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 docsify

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2021-23342: XSS in docsify 6.1 medium 4.12.0 01 Mar 2021
CVE-2020-7680: Cross-site Scripting in docsify 6.1 medium 4.11.4 18 May 2021
Docsify vulnerable to cross-site scripting due to mishandled encoding 6.1 medium 4.12.2 24 May 2022

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 docsify

Is docsify safe to use?

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

Vulert scores docsify 82/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 docsify affected?

No. 5.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 docsify should I use?

5.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 docsify have?

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

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

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