VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

slpjs: vulnerability history, versions and safety

slpjs is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 112 releases, from Nov 2019 to Jul 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 C3
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 slpjs vulnerabilities

Vulert verdict on slpjs 0.27.11 i

Updated on 23 Oct 2026

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

Package health score 47/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 0.27.11 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 30 Jul 2020 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Stars 41 i
  • OpenSSF scorecard 0/10 i
  • Last release 70 months ago i
  • Licence ISC 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 slpjs, 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
0.27.11 09 Dec 2020 none ISC — Details →
0.27.9 24 Nov 2020 none ISC — Details →
0.27.8 11 Sep 2020 none ISC — Details →
0.27.7 11 Sep 2020 none ISC — Details →
0.27.6 11 Sep 2020 none ISC — Details →
0.27.5 11 Sep 2020 none ISC — Details →
0.27.4 29 Jul 2020 none ISC — Details →
0.27.3 07 Jul 2020 C1 ISC Yes Details →
0.27.2 29 Apr 2020 C1 ISC Yes Details →
0.27.1 25 Apr 2020 C2 ISC Yes Details →
0.27.0 07 Apr 2020 C2 ISC Yes Details →
0.26.0 07 Apr 2020 C2 ISC Yes Details →
0.25.6 06 Apr 2020 C2 ISC Yes Details →
0.25.5 06 Apr 2020 C2 ISC Yes Details →
0.25.4 06 Apr 2020 C2 ISC Yes Details →
0.25.3 06 Apr 2020 C2 ISC Yes Details →
0.25.2 31 Mar 2020 C2 ISC Yes Details →
0.25.1 31 Mar 2020 C2 ISC Yes Details →
0.25.0 31 Mar 2020 C2 ISC Yes Details →
0.24.3 06 Feb 2020 C2 ISC Yes Details →
0.24.2 01 Feb 2020 C2 ISC Yes Details →
0.24.1 01 Feb 2020 C2 ISC Yes Details →
0.24.0 31 Jan 2020 C2 ISC Yes Details →
0.23.3 31 Jan 2020 C2 ISC Yes Details →
0.23.2 29 Jan 2020 C2 ISC Yes Details →
0.22.6 29 Jan 2020 C2 ISC Yes Details →
0.22.5 02 Jan 2020 C2 ISC Yes Details →
0.22.4 02 Jan 2020 C2 ISC Yes Details →
0.23.0 27 Nov 2019 C2 ISC Yes Details →
0.22.3 21 Nov 2019 C2 ISC Yes Details →
0.22.2 21 Nov 2019 C2 ISC Yes Details →
0.22.1 21 Nov 2019 C2 ISC Yes Details →
0.22.0 08 Nov 2019 C2 ISC Yes Details →
0.21.4 28 Oct 2019 C2 MIT Yes Details →
0.21.3 23 Sep 2019 C3 MIT Yes Details →
0.21.2 13 Aug 2019 C3 MIT Yes Details →
0.21.1 25 Jul 2019 C3 MIT Yes Details →
0.21.0 18 Jul 2019 C3 MIT Yes Details →
0.20.5 16 Jul 2019 C3 MIT Yes Details →
0.20.4 16 Jul 2019 C3 MIT Yes Details →
0.20.3 15 Jul 2019 C3 MIT Yes Details →
0.20.2 15 Jul 2019 C3 MIT Yes Details →
0.20.1 13 Jul 2019 C3 MIT Yes Details →
0.20.0 13 Jul 2019 C3 MIT Yes Details →
0.19.0 11 Jul 2019 C3 MIT Yes Details →
0.18.4 11 Jun 2019 C3 MIT Yes Details →
0.18.3 31 May 2019 C3 MIT Yes Details →
0.18.2 30 May 2019 C3 MIT Yes Details →
0.18.1 28 May 2019 C3 MIT Yes Details →
0.18.0 22 May 2019 C3 MIT Yes Details →
0.17.0 17 May 2019 C3 MIT Yes Details →
0.16.3 09 May 2019 C3 MIT Yes Details →
0.16.2 08 May 2019 C3 MIT Yes Details →
0.16.1 07 May 2019 C3 MIT Yes Details →
0.16.0 05 May 2019 C3 MIT Yes Details →
0.15.13 01 May 2019 C3 MIT Yes Details →
0.15.12 13 Apr 2019 C3 MIT Yes Details →
0.15.11 11 Apr 2019 C3 MIT Yes Details →
0.15.10 05 Apr 2019 C3 MIT Yes Details →
0.15.9 28 Mar 2019 C3 MIT Yes Details →
0.15.8 26 Mar 2019 C3 MIT Yes Details →
0.15.7 26 Mar 2019 C3 MIT Yes Details →
0.15.6 22 Mar 2019 C3 MIT Yes Details →
0.15.5 19 Mar 2019 C3 MIT Yes Details →
0.15.4 08 Mar 2019 C3 MIT Yes Details →
0.15.3 04 Mar 2019 C3 MIT Yes Details →
0.15.0 28 Feb 2019 C3 MIT Yes Details →
0.14.0 25 Feb 2019 C3 MIT Yes Details →
0.13.2 16 Feb 2019 C3 MIT Yes Details →
0.13.0 11 Feb 2019 C3 MIT Yes Details →
0.12.3 11 Feb 2019 C3 MIT Yes Details →
0.12.2 07 Feb 2019 C3 MIT Yes Details →
0.12.1 07 Feb 2019 C3 MIT Yes Details →
0.12.0 07 Feb 2019 C3 MIT Yes Details →
0.11.6 06 Feb 2019 C3 MIT Yes Details →
0.11.5 06 Feb 2019 C3 MIT Yes Details →
0.11.4 06 Feb 2019 C3 MIT Yes Details →
0.11.3 06 Feb 2019 C3 MIT Yes Details →
0.11.2 05 Feb 2019 C3 MIT Yes Details →
0.11.1 05 Feb 2019 C3 MIT Yes Details →
0.11.0 05 Feb 2019 C3 MIT Yes Details →
0.10.3 04 Feb 2019 C3 MIT Yes Details →
0.10.2 31 Jan 2019 C3 MIT Yes Details →
0.10.1 30 Jan 2019 C3 MIT Yes Details →
0.10.0 30 Jan 2019 C3 MIT Yes Details →
0.9.1 25 Jan 2019 C3 MIT Yes Details →
0.9.0 22 Jan 2019 C3 MIT Yes Details →
0.2.2 10 Nov 2018 C3 MIT Yes Details →
0.2.1 09 Nov 2018 C3 MIT Yes Details →
0.2.0 31 Oct 2018 C3 MIT Yes Details →
0.1.7 17 Oct 2018 C3 MIT Yes Details →
0.1.6 11 Oct 2018 C3 MIT Yes Details →
0.1.5 08 Oct 2018 C3 MIT Yes Details →
0.1.4 22 Sep 2018 C3 MIT Yes Details →
0.1.3 11 Sep 2018 C3 MIT Yes Details →
0.1.2 11 Sep 2018 C3 MIT Yes Details →
0.1.1 07 Sep 2018 C3 MIT Yes Details →
0.1.0 06 Sep 2018 C3 MIT Yes Details →
0.0.21 05 Sep 2018 C3 MIT Yes Details →
0.0.20 05 Sep 2018 C3 MIT Yes Details →
0.0.19 05 Sep 2018 C3 — Yes Details →
0.0.18 05 Sep 2018 C3 — Yes Details →
0.0.17 05 Sep 2018 C3 — Yes Details →
0.0.16 05 Sep 2018 C3 — Yes Details →
0.0.15 05 Sep 2018 C3 — Yes Details →
0.0.14 04 Sep 2018 C3 — Yes Details →
0.0.13 04 Sep 2018 C3 — Yes Details →
0.0.12 04 Sep 2018 C3 — Yes Details →
0.0.11 30 Aug 2018 C3 — Yes Details →
0.0.10 30 Aug 2018 C3 — Yes Details →
0.0.9 29 Aug 2018 C3 — Yes Details →
0.0.8 29 Aug 2018 C3 — Yes Details →
0.0.7 29 Aug 2018 C3 — Yes Details →
0.0.6 28 Aug 2018 C3 — Yes Details →
0.0.5 27 Aug 2018 C3 — Yes Details →
0.0.4 27 Aug 2018 C3 — Yes Details →
0.0.3 27 Aug 2018 C3 — Yes Details →
0.0.2 27 Aug 2018 C3 — Yes Details →
0.0.1 26 Aug 2018 C3 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 2

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 slpjs

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-11071: Vulnerability in slpjs package allows false-negative validation results in MINT transactions 8.6 critical 0.27.2 12 May 2020
CVE-2020-15130: False-positive validity for NFT1 genesis transactions in slpjs 7.5 critical 0.27.4 30 Jul 2020
CVE-2019-16762: Critical vulnerability in slpjs package 5.7 critical 0.21.4 15 Nov 2019

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 slpjs

Is slpjs safe to use?

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

Vulert scores slpjs 47/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).

Is the latest version of slpjs affected?

No. 0.27.11, 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 slpjs should I use?

0.27.11 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 slpjs have?

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

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

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