VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

harp: vulnerability history, versions and safety

harp is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from Jun 2019 to Sep 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 M3
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 harp vulnerabilities

Vulert verdict on harp 0.50.1 i

Updated on 23 Oct 2026

Careful: 0.50.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.50.1 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 02 Sep 2020 i
  • Highest CVSS 5.3 i
  • With no published fix 1 i
  • Depended on by 5 packages i
  • Stars 4,997 i
  • OpenSSF scorecard 2/10 i
  • Last release 3 months ago i
  • Licence MIT i
  • Similar names sharp 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 harp, 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.50.1 06 Jul 2026 M1 MIT No Details →
0.50.0 05 Jul 2026 M1 MIT No Details →
0.49.3 28 Jun 2026 M1 MIT No Details →
0.49.2 28 Jun 2026 M1 MIT No Details →
0.49.1 28 Jun 2026 M1 MIT No Details →
0.49.0 28 Jun 2026 M1 MIT No Details →
0.48.1 28 Jun 2026 M1 MIT No Details →
0.48.0 28 Jun 2026 M1 MIT No Details →
0.47.2 17 Feb 2026 M1 MIT No Details →
0.47.1 17 Feb 2026 M1 MIT No Details →
0.47.0 25 Jun 2025 M1 MIT No Details →
0.46.1 13 Jan 2023 M1 MIT No Details →
0.46.0 10 Sep 2022 M1 MIT No Details →
0.45.0 09 Sep 2022 M1 MIT No Details →
0.44.0 09 Sep 2022 M1 MIT No Details →
0.43.0 09 Sep 2022 M1 MIT No Details →
0.42.0 14 Aug 2022 M1 MIT No Details →
0.41.2 17 Jan 2022 M1 MIT No Details →
0.41.0 10 Jun 2021 M1 MIT No Details →
0.40.3 07 Jun 2021 M1 MIT No Details →
0.40.2 02 Jun 2021 M2 MIT No Details →
0.40.1 31 May 2021 M3 MIT No Details →
0.40.0 30 May 2021 M3 MIT No Details →
0.34.0 21 May 2021 M3 MIT No Details →
0.33.0 07 Nov 2020 M3 MIT No Details →
0.32.0 14 Apr 2020 M3 MIT No Details →
0.31.0 10 Oct 2019 M3 MIT No Details →
0.30.1 04 Aug 2019 M3 MIT No Details →
0.30.0 28 Mar 2019 M3 MIT No Details →
0.29.0 26 Sep 2018 M3 MIT No Details →
0.28.1 14 Sep 2018 M3 MIT No Details →
0.28.0 14 Sep 2018 M3 MIT No Details →
0.27.0 19 Jun 2018 M3 MIT No Details →
0.26.0 24 May 2018 M3 MIT No Details →
0.25.0 03 Dec 2017 M3 MIT No Details →
0.24.1 30 Sep 2017 M3 MIT No Details →
0.24.0 03 Jun 2017 M3 MIT No Details →
0.23.0 25 Nov 2016 M3 MIT No Details →
0.22.0 13 Nov 2016 M3 MIT No Details →
0.21.0 10 Oct 2016 M3 MIT No Details →
0.21.0-pre.1 16 Sep 2016 M3 MIT No Details →
0.21.0-pre.0 09 Sep 2016 M3 MIT No Details →
0.20.3 05 Apr 2016 M3 MIT No Details →
0.20.2 04 Apr 2016 M3 MIT No Details →
0.20.1 20 Nov 2015 M3 MIT No Details →
0.20.0 16 Nov 2015 M3 MIT No Details →
0.19.0 18 Sep 2015 M3 MIT No Details →
0.18.0 10 Sep 2015 M3 MIT No Details →
0.17.0 20 Apr 2015 M3 MIT No Details →
0.16.0 20 Apr 2015 M3 MIT No Details →
0.15.2 14 Feb 2015 M3 MIT No Details →
0.15.1 11 Feb 2015 M3 MIT No Details →
0.15.0 07 Feb 2015 M3 MIT No Details →
0.14.0 23 Sep 2014 M3 MIT No Details →
0.13.0 11 Aug 2014 M3 MIT No Details →
0.12.1 29 Mar 2014 M3 MIT No Details →
0.12.0 27 Mar 2014 M3 MIT No Details →
0.11.2 30 Jan 2014 M3 MIT No Details →
0.11.1 08 Jan 2014 M3 MIT No Details →
0.11.0 19 Dec 2013 M3 MIT No Details →
0.10.1 19 Nov 2013 M3 MIT No Details →
0.10.0 11 Nov 2013 M3 MIT No Details →
0.9.5 09 Nov 2013 M3 MIT No Details →
0.9.4 21 Oct 2013 M3 MIT No Details →
0.9.3 14 Sep 2013 M3 MIT No Details →
0.9.2 05 Sep 2013 M3 MIT No Details →
0.9.1 19 Aug 2013 M3 MIT No Details →
0.9.0 17 Aug 2013 M3 MIT No Details →
0.8.13 29 Jul 2013 M3 MIT No Details →
0.8.12 23 Jul 2013 M3 MIT No Details →
0.8.11 19 Jul 2013 M3 MIT No Details →
0.8.10 19 Jul 2013 M3 MIT No Details →
0.8.9 19 Jul 2013 M3 MIT No Details →
0.8.8 18 Jul 2013 M3 MIT No Details →
0.8.7 18 Jul 2013 M3 MIT No Details →
0.8.6 18 Jul 2013 M3 MIT No Details →
0.8.5 17 Jul 2013 M3 MIT No Details →
0.8.4 17 Jul 2013 M3 MIT No Details →
0.8.3 16 Jul 2013 M3 MIT No Details →
0.8.2 15 Jul 2013 M3 MIT No Details →
0.8.1 09 Jul 2013 M3 MIT No Details →
0.8.0 07 Jul 2013 M3 MIT No Details →
0.7.10 20 Jun 2013 M3 MIT No Details →
0.7.9 11 Jun 2013 M3 MIT No Details →
0.7.8 11 Jun 2013 M3 MIT No Details →
0.7.7 27 May 2013 M3 MIT No Details →
0.7.6 11 May 2013 M3 MIT No Details →
0.7.5 02 May 2013 M3 MIT No Details →
0.7.4 02 May 2013 M3 MIT No Details →
0.7.3 22 Apr 2013 M3 MIT No Details →
0.7.2 22 Apr 2013 M3 MIT No Details →
0.7.1 19 Apr 2013 M3 MIT No Details →
0.7.0 19 Apr 2013 M3 MIT No Details →
0.6.2 15 Mar 2013 M3 MIT No Details →
0.6.1 15 Mar 2013 M3 MIT No Details →
0.6.0 13 Mar 2013 M3 MIT No Details →
0.5.6 13 Mar 2013 M3 MIT No Details →
0.5.5 11 Mar 2013 M3 MIT No Details →
0.5.4 05 Mar 2013 M3 MIT No Details →
0.5.3 03 Mar 2013 M3 MIT No Details →
0.5.2 22 Feb 2013 M3 — No Details →
0.5.1 18 Feb 2013 M3 — No Details →
0.5.0 13 Feb 2013 M3 — No Details →
0.4.5 23 Jan 2013 M3 — No Details →
0.4.4 19 Jan 2013 M3 — No Details →
0.4.3 13 Jan 2013 M3 — No Details →
0.4.2 20 Dec 2012 M3 — No Details →
0.4.1 16 Dec 2012 M3 — No Details →
0.4.0 16 Dec 2012 M3 — No Details →
0.3.6 11 Dec 2012 M3 — No Details →
0.3.5 08 Dec 2012 M3 — No Details →
0.3.4 08 Dec 2012 M3 — No Details →
0.3.3 08 Dec 2012 M3 — No Details →
0.3.2 08 Dec 2012 M3 — No Details →
0.3.1 08 Dec 2012 M3 — No Details →
0.3.0 08 Dec 2012 M3 — No Details →
0.2.6 08 Dec 2012 M3 — No Details →
0.2.5 08 Dec 2012 M3 — No Details →
0.2.4 08 Dec 2012 M3 — No Details →
0.2.3 07 Dec 2012 M3 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2020 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 harp

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2019-5437: Unauthorized File Access in harp 5.3 medium 0.40.2 13 Jun 2019
CVE-2019-5438: Unauthorized File Access in harp 5.3 medium 0.40.3 13 Jun 2019
Cross-Site Scripting Vulnerability in harp N/A medium No fix published 02 Sep 2020

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 harp

Is harp safe to use?

Vulert records 3 vulnerabilities for harp in npm: 0 critical, 0 high, 3 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is harp's Vulert package health score?

Vulert scores harp 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of harp affected?

Yes. 0.50.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of harp should I use?

0.50.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 harp have?

3 vulnerabilities are recorded for harp 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 harp vulnerabilities disclosed?

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

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