VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

karma: vulnerability history, versions and safety

karma is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 110 releases, first recorded in Feb 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
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 karma vulnerabilities

Vulert verdict on karma 6.4.4 i

Updated on 22 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 6.4.4 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 26 Feb 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 255 packages i
  • Stars 11,955 i
  • OpenSSF scorecard 3/10 i
  • Last release 26 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 karma, 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
6.4.4 29 Jul 2024 none MIT — Details →
6.4.3 24 Feb 2024 none MIT — Details →
6.4.2 21 Apr 2023 none MIT — Details →
6.4.1 19 Sep 2022 none MIT — Details →
6.4.0 14 Jun 2022 none MIT — Details →
6.3.20 13 May 2022 none MIT — Details →
6.3.19 19 Apr 2022 none MIT — Details →
6.3.18 13 Apr 2022 none MIT — Details →
6.3.17 28 Feb 2022 none MIT — Details →
6.3.16 10 Feb 2022 none MIT — Details →
6.3.15 05 Feb 2022 M1 MIT Yes Details →
6.3.14 05 Feb 2022 M1 MIT Yes Details →
6.3.13 31 Jan 2022 M2 MIT Yes Details →
6.3.12 24 Jan 2022 M2 MIT Yes Details →
6.3.11 13 Jan 2022 M2 MIT Yes Details →
6.3.10 08 Jan 2022 M2 MIT Yes Details →
6.3.9 16 Nov 2021 M2 MIT Yes Details →
6.3.8 07 Nov 2021 M2 MIT Yes Details →
6.3.7 01 Nov 2021 M2 MIT Yes Details →
6.3.6 25 Oct 2021 M2 MIT Yes Details →
6.3.5 20 Oct 2021 M2 MIT Yes Details →
6.3.4 14 Jun 2021 M2 MIT Yes Details →
6.3.3 01 Jun 2021 M2 MIT Yes Details →
6.3.2 29 Mar 2021 M2 MIT Yes Details →
6.3.1 24 Mar 2021 M2 MIT Yes Details →
6.3.0 23 Mar 2021 M2 MIT Yes Details →
6.2.0 10 Mar 2021 M2 MIT Yes Details →
6.1.2 09 Mar 2021 M2 MIT Yes Details →
6.1.1 12 Feb 2021 M2 MIT Yes Details →
6.1.0 03 Feb 2021 M2 MIT Yes Details →
6.0.4 01 Feb 2021 M2 MIT Yes Details →
6.0.3 27 Jan 2021 M2 MIT Yes Details →
6.0.2 25 Jan 2021 M2 MIT Yes Details →
6.0.1 20 Jan 2021 M2 MIT Yes Details →
6.0.0 13 Jan 2021 M2 MIT Yes Details →
5.2.3 25 Sep 2020 M2 MIT Yes Details →
5.2.2 08 Sep 2020 M2 MIT Yes Details →
5.2.1 02 Sep 2020 M2 MIT Yes Details →
5.2.0 31 Aug 2020 M2 MIT Yes Details →
5.1.1 28 Jul 2020 M2 MIT Yes Details →
5.1.0 11 Jun 2020 M2 MIT Yes Details →
5.0.9 19 May 2020 M2 MIT Yes Details →
5.0.8 18 May 2020 M2 MIT Yes Details →
5.0.7 16 May 2020 M2 MIT Yes Details →
5.0.6 16 May 2020 M2 MIT Yes Details →
5.0.5 07 May 2020 M2 MIT Yes Details →
5.0.4 30 Apr 2020 M2 MIT Yes Details →
5.0.3 29 Apr 2020 M2 MIT Yes Details →
5.0.2 16 Apr 2020 M2 MIT Yes Details →
5.0.1 10 Apr 2020 M2 MIT Yes Details →
5.0.0 09 Apr 2020 M2 MIT Yes Details →
4.4.1 18 Oct 2019 M2 MIT Yes Details →
4.4.0 17 Oct 2019 M2 MIT Yes Details →
4.3.0 27 Aug 2019 M2 MIT Yes Details →
4.2.0 12 Jul 2019 M2 MIT Yes Details →
4.1.0 15 Apr 2019 M2 MIT Yes Details →
4.0.1 28 Feb 2019 M2 MIT Yes Details →
4.0.0 23 Jan 2019 M2 MIT Yes Details →
3.1.4 17 Dec 2018 M2 MIT Yes Details →
3.1.3 01 Dec 2018 M2 MIT Yes Details →
3.1.2 01 Dec 2018 M2 MIT Yes Details →
3.1.1 23 Oct 2018 M2 MIT Yes Details →
3.1.0 22 Oct 2018 M2 MIT Yes Details →
3.0.0 09 Aug 2018 M2 MIT Yes Details →
2.0.5 24 Jul 2018 M2 MIT Yes Details →
2.0.4 21 Jun 2018 M2 MIT Yes Details →
2.0.3 15 Jun 2018 M2 MIT Yes Details →
2.0.2 19 Apr 2018 M2 MIT Yes Details →
2.0.0 21 Dec 2017 M2 MIT Yes Details →
1.7.1 30 Aug 2017 M2 MIT Yes Details →
1.7.0 06 May 2017 M2 MIT Yes Details →
1.6.0 05 Apr 2017 M2 MIT Yes Details →
1.5.0 20 Feb 2017 M2 MIT Yes Details →
1.4.1 29 Jan 2017 M2 MIT Yes Details →
1.4.0 14 Jan 2017 M2 MIT Yes Details →
1.3.0 09 Sep 2016 M2 MIT Yes Details →
1.2.0 11 Aug 2016 M2 MIT Yes Details →
1.1.2 26 Jul 2016 M2 MIT Yes Details →
1.1.1 07 Jul 2016 M2 MIT Yes Details →
1.1.0 26 Jun 2016 M2 MIT Yes Details →
1.0.0 23 Jun 2016 M2 MIT Yes Details →
0.13.22 08 Mar 2016 M2 MIT Yes Details →
0.13.21 12 Feb 2016 M2 MIT Yes Details →
0.13.20 12 Feb 2016 M2 MIT Yes Details →
0.13.19 06 Jan 2016 M2 MIT Yes Details →
0.13.18 05 Jan 2016 M2 MIT Yes Details →
0.13.17 04 Jan 2016 M2 MIT Yes Details →
0.13.16 24 Dec 2015 M2 MIT Yes Details →
0.13.15 03 Nov 2015 M2 MIT Yes Details →
0.13.14 22 Oct 2015 M2 MIT Yes Details →
0.13.13 22 Oct 2015 M2 MIT Yes Details →
0.13.12 22 Oct 2015 M2 MIT Yes Details →
0.13.11 14 Oct 2015 M2 MIT Yes Details →
0.13.10 21 Sep 2015 M2 MIT Yes Details →
0.13.9 11 Aug 2015 M2 MIT Yes Details →
0.13.8 06 Aug 2015 M2 MIT Yes Details →
0.13.7 05 Aug 2015 M2 MIT Yes Details →
0.13.6 05 Aug 2015 M2 MIT Yes Details →
0.13.5 04 Aug 2015 M2 MIT Yes Details →
0.13.4 04 Aug 2015 M2 MIT Yes Details →
0.13.3 22 Jul 2015 M2 — Yes Details →
0.13.2 17 Jul 2015 M2 — Yes Details →
0.13.1 16 Jul 2015 M2 — Yes Details →
0.13.0 15 Jul 2015 M2 — Yes Details →
0.13.0-rc.9 13 Jul 2015 M2 — Yes Details →
0.13.0-rc.8 09 Jul 2015 M2 — Yes Details →
0.13.0-rc.7 08 Jul 2015 M2 — Yes Details →
0.13.0-rc.6 25 Jun 2015 M2 — Yes Details →
0.13.0-rc.5 23 Jun 2015 M2 — Yes Details →
0.12.37 23 Jun 2015 M2 — Yes Details →
0.13.0-rc.4 04 Jun 2015 M2 — Yes Details →
0.12.36 04 Jun 2015 M2 — Yes Details →
0.13.0-rc.3 29 May 2015 M2 — Yes Details →
0.12.35 29 May 2015 M2 — Yes Details →
0.13.0-rc.2 29 May 2015 M2 — Yes Details →
0.12.34 29 May 2015 M2 — Yes Details →
0.13.0-rc.1 27 May 2015 M2 — Yes Details →
0.12.33 26 May 2015 M2 — Yes Details →
0.13.0-rc.0 26 May 2015 M2 — Yes Details →
0.12.32 24 Feb 2015 M2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for karma

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-0437: Cross-site Scripting in karma 6.1 medium 6.3.14 06 Feb 2022
CVE-2021-23495: Open Redirect in karma 5.4 medium 6.3.16 26 Feb 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: 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 karma

Is karma safe to use?

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

Vulert scores karma 75/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 karma affected?

No. 6.4.4, 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 karma should I use?

6.4.4 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 karma have?

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

0 vulnerabilities were recorded for karma in the last 12 months, and the oldest entry in this database dates to 06 Feb 2022. 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 karma 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 karma for upcoming vulnerabilities?

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