VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

keystone: vulnerability history, versions and safety

keystone is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 115 releases, from Nov 2017 to Aug 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H3 M4
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 keystone vulnerabilities

Vulert verdict on keystone 4.2.1 i

Updated on 22 Oct 2026

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

Package health score 67/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Moderate

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

  • Current release 4.2.1 — unaffected i
  • Vulnerabilities on record 7 over 2 years · 0 in the last year i
  • Latest disclosure 20 Aug 2020 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 14 packages i
  • Stars 9,980 i
  • OpenSSF scorecard 4/10 i
  • Last release 87 months ago i
  • Licence MIT 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 keystone, 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
4.2.1 15 Jul 2019 none MIT — Details →
4.2.0 15 Jul 2019 none MIT — Details →
4.1.1 23 Jun 2019 none MIT — Details →
4.1.0 19 May 2019 none MIT — Details →
4.0.0 25 Jul 2018 none MIT — Details →
4.0.0-rc.1 06 Jul 2018 M2 MIT Yes Details →
4.0.0-rc.0 22 Jun 2018 M2 MIT Yes Details →
4.0.0-beta.8 22 Jan 2018 M2 MIT Yes Details →
4.0.0-beta.7 23 Oct 2017 M2 MIT Yes Details →
4.0.0-beta.5 25 Jan 2017 H2 M3 MIT Yes Details →
4.0.0-beta.4 02 Dec 2016 H2 M3 MIT Yes Details →
4.0.0-beta.3 25 Sep 2016 H2 M3 MIT Yes Details →
4.0.0-beta.2 06 Sep 2016 H2 M3 MIT Yes Details →
4.0.0-beta.1 25 Aug 2016 H2 M3 MIT Yes Details →
0.3.22 22 Jul 2016 H2 M3 MIT Yes Details →
0.3.21 19 Jun 2016 H2 M3 MIT Yes Details →
0.3.20 17 Jun 2016 H2 M3 MIT Yes Details →
0.3.19 04 May 2016 H2 M3 MIT Yes Details →
0.3.18 27 Apr 2016 H2 M3 MIT Yes Details →
0.3.17 23 Mar 2016 H2 M3 MIT Yes Details →
0.3.16 04 Dec 2015 H2 M3 MIT Yes Details →
0.3.15 15 Oct 2015 H3 M4 MIT Yes Details →
0.3.14 25 Aug 2015 H3 M4 MIT Yes Details →
0.3.13 03 Aug 2015 H3 M4 MIT Yes Details →
0.3.12 25 Jun 2015 H3 M4 MIT Yes Details →
0.3.11 12 Jun 2015 H3 M4 MIT Yes Details →
0.3.10 19 May 2015 H3 M4 MIT Yes Details →
0.3.9 16 May 2015 H3 M4 MIT Yes Details →
0.3.8 23 Apr 2015 H3 M4 MIT Yes Details →
0.3.7 23 Apr 2015 H3 M4 MIT Yes Details →
0.3.6 14 Apr 2015 H3 M4 MIT Yes Details →
0.3.5 12 Apr 2015 H3 M4 MIT Yes Details →
0.3.4 10 Mar 2015 H3 M4 MIT Yes Details →
0.3.3 08 Mar 2015 H3 M4 MIT Yes Details →
0.3.2 27 Feb 2015 H3 M4 MIT Yes Details →
0.3.1 13 Feb 2015 H3 M4 MIT Yes Details →
0.3.0 10 Feb 2015 H3 M4 MIT Yes Details →
0.2.42 20 Jan 2015 H3 M4 MIT Yes Details →
0.2.41 18 Jan 2015 H3 M4 MIT Yes Details →
0.2.40 31 Dec 2014 H3 M4 MIT Yes Details →
0.2.39 20 Dec 2014 H3 M4 MIT Yes Details →
0.2.38 19 Dec 2014 H3 M4 MIT Yes Details →
0.2.37 19 Dec 2014 H3 M4 MIT Yes Details →
0.2.36 07 Dec 2014 H3 M4 MIT Yes Details →
0.2.35 03 Dec 2014 H3 M4 MIT Yes Details →
0.2.34 29 Nov 2014 H3 M4 MIT Yes Details →
0.2.33 04 Nov 2014 H3 M4 MIT Yes Details →
0.2.32 16 Oct 2014 H3 M4 MIT Yes Details →
0.2.31 14 Oct 2014 H3 M4 MIT Yes Details →
0.2.30 02 Oct 2014 H3 M4 MIT Yes Details →
0.2.29 30 Sep 2014 H3 M4 MIT Yes Details →
0.2.28 12 Sep 2014 H3 M4 MIT Yes Details →
0.2.27 30 Aug 2014 H3 M4 MIT Yes Details →
0.2.26 14 Aug 2014 H3 M4 MIT Yes Details →
0.2.25 27 Jul 2014 H3 M4 MIT Yes Details →
0.2.24 25 Jul 2014 H3 M4 MIT Yes Details →
0.2.23 20 Jul 2014 H3 M4 MIT Yes Details →
0.2.22 28 Jun 2014 H3 M4 MIT Yes Details →
0.2.21 16 Jun 2014 H3 M4 MIT Yes Details →
0.2.20 06 Jun 2014 H3 M4 MIT Yes Details →
0.2.19 28 May 2014 H3 M4 MIT Yes Details →
0.2.18 21 May 2014 H3 M4 MIT Yes Details →
0.2.17 19 May 2014 H3 M4 MIT Yes Details →
0.2.16 14 May 2014 H3 M4 MIT Yes Details →
0.2.15 13 May 2014 H3 M4 MIT Yes Details →
0.2.14 15 Apr 2014 H3 M4 MIT Yes Details →
0.2.13 03 Apr 2014 H3 M4 MIT Yes Details →
0.2.12 02 Apr 2014 H3 M4 MIT Yes Details →
0.2.11 02 Apr 2014 H3 M4 MIT Yes Details →
0.2.10 18 Mar 2014 H3 M4 MIT Yes Details →
0.2.9 18 Mar 2014 H3 M4 MIT Yes Details →
0.2.8 12 Mar 2014 H3 M4 MIT Yes Details →
0.2.7 11 Mar 2014 H3 M4 MIT Yes Details →
0.2.6 25 Feb 2014 H3 M4 MIT Yes Details →
0.2.5 17 Feb 2014 H3 M4 MIT Yes Details →
0.2.4 15 Feb 2014 H3 M4 MIT Yes Details →
0.2.3 10 Feb 2014 H3 M4 MIT Yes Details →
0.2.2 05 Feb 2014 H3 M4 MIT Yes Details →
0.2.1 04 Feb 2014 H3 M4 MIT Yes Details →
0.2.0 25 Jan 2014 H3 M4 MIT Yes Details →
0.1.55 30 Dec 2013 H3 M4 MIT Yes Details →
0.1.54 23 Dec 2013 H3 M4 MIT Yes Details →
0.1.53 22 Dec 2013 H3 M4 MIT Yes Details →
0.1.52 12 Dec 2013 H3 M4 MIT Yes Details →
0.1.51 10 Dec 2013 H3 M4 MIT Yes Details →
0.1.50 09 Dec 2013 H3 M4 MIT Yes Details →
0.1.49 04 Dec 2013 H3 M4 MIT Yes Details →
0.1.48 03 Dec 2013 H3 M4 MIT Yes Details →
0.1.47 02 Dec 2013 H3 M4 MIT Yes Details →
0.1.46 27 Nov 2013 H3 M4 MIT Yes Details →
0.1.45 20 Nov 2013 H3 M4 MIT Yes Details →
0.1.44 19 Nov 2013 H3 M4 MIT Yes Details →
0.1.43 19 Nov 2013 H3 M4 MIT Yes Details →
0.1.42 18 Nov 2013 H3 M4 MIT Yes Details →
0.1.41 18 Nov 2013 H3 M4 MIT Yes Details →
0.1.40 14 Nov 2013 H3 M4 MIT Yes Details →
0.1.39 06 Nov 2013 H3 M4 MIT Yes Details →
0.1.38 05 Nov 2013 H3 M4 MIT Yes Details →
0.1.37 04 Nov 2013 H3 M4 MIT Yes Details →
0.1.36 02 Nov 2013 H3 M4 MIT Yes Details →
0.1.35 31 Oct 2013 H3 M4 — Yes Details →
0.1.34 24 Oct 2013 H3 M4 — Yes Details →
0.1.33 21 Oct 2013 H3 M4 — Yes Details →
0.1.32 19 Oct 2013 H3 M4 — Yes Details →
0.1.31 18 Oct 2013 H3 M4 — Yes Details →
0.1.30 18 Oct 2013 H3 M4 — Yes Details →
0.1.29 17 Oct 2013 H3 M4 — Yes Details →
0.1.28 15 Oct 2013 H3 M4 — Yes Details →
0.1.27 09 Oct 2013 H3 M4 — Yes Details →
0.1.26 09 Oct 2013 H3 M4 — Yes Details →
0.1.25 06 Oct 2013 H3 M4 — Yes Details →
0.1.24 30 Sep 2013 H3 M4 — Yes Details →
0.1.23 27 Sep 2013 H3 M4 — Yes Details →
0.1.22 26 Sep 2013 H3 M4 — Yes Details →
0.1.21 25 Sep 2013 H3 M4 — Yes Details →
0.1.20 23 Sep 2013 H3 M4 — Yes Details →
0.1.19 18 Sep 2013 H3 M4 — Yes Details →
0.1.18 18 Sep 2013 H3 M4 — Yes Details →
0.1.17 17 Sep 2013 H3 M4 — Yes Details →
0.1.16 17 Sep 2013 H3 M4 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 4
  • 2018 1
  • 2020 2

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

03 Vulnerabilities

Recorded vulnerabilities for keystone

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-15879: Keystone CSV Injection Vulnerability 8.8 high 4.0.0-beta7 16 Nov 2017
CVE-2017-16570: Cross-Site Request Forgery (CSRF) in keystone 8.8 high 4.0.0-beta.7 30 Nov 2017
CVE-2015-9240: Authentication Weakness in keystone 7.5 high 0.3.16 07 Jun 2018
CVE-2017-15878: Cross-Site Scripting in keystone 6.1 medium 4.0.0 15 Nov 2017
CVE-2017-15881: Cross-Site Scripting in keystone 4.8 medium 4.0.0-beta7 16 Nov 2017

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 keystone

Is keystone safe to use?

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

Vulert scores keystone 67/100, which reads as usable, but worth attention. 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 keystone affected?

No. 4.2.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 keystone should I use?

4.2.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 keystone have?

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

0 vulnerabilities were recorded for keystone in the last 12 months, and the oldest entry in this database dates to 15 Nov 2017. 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 keystone 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 keystone for upcoming vulnerabilities?

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