VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

camelcase-keys: vulnerability history, versions and safety

camelcase-keys is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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 camelcase-keys vulnerabilities

Vulert verdict on camelcase-keys 10.0.3 i

Updated on 23 Oct 2026

Good news: 10.0.3, the version you would install today, has no known vulnerabilities.

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 10.0.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 225 packages i
  • Stars 759 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month 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 camelcase-keys, 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
10.0.3 20 Sep 2026 none MIT — Details →
10.0.2 25 Jan 2026 none MIT — Details →
10.0.1 02 Nov 2025 none MIT — Details →
10.0.0 09 Sep 2025 none MIT — Details →
9.1.3 13 Jan 2024 none MIT — Details →
9.1.2 18 Oct 2023 none MIT — Details →
9.1.1 17 Oct 2023 none MIT — Details →
9.1.0 29 Sep 2023 none MIT — Details →
9.0.0 16 Aug 2023 none MIT — Details →
8.0.2 29 Aug 2022 none MIT — Details →
8.0.1 22 Jun 2022 none MIT — Details →
8.0.0 06 Jun 2022 none MIT — Details →
7.0.2 01 Feb 2022 none MIT — Details →
7.0.1 04 Oct 2021 none MIT — Details →
7.0.0 25 Jun 2021 none MIT — Details →
6.2.2 03 Apr 2020 none MIT — Details →
6.2.1 06 Mar 2020 none MIT — Details →
6.2.0 05 Mar 2020 none MIT — Details →
6.1.2 30 Jan 2020 none MIT — Details →
6.1.1 08 Nov 2019 none MIT — Details →
6.1.0 18 Oct 2019 none MIT — Details →
6.0.1 31 Jul 2019 none MIT — Details →
6.0.0 11 Jun 2019 none MIT — Details →
5.2.0 18 Apr 2019 none MIT — Details →
5.1.0 09 Apr 2019 none MIT — Details →
5.0.0 16 Oct 2018 none MIT — Details →
4.2.0 19 Nov 2017 none MIT — Details →
4.1.0 31 Mar 2017 none MIT — Details →
4.0.0 17 Sep 2016 none MIT — Details →
3.0.0 10 May 2016 none MIT — Details →
2.1.0 15 Mar 2016 none MIT — Details →
2.0.0 15 Nov 2015 none MIT — Details →
1.0.0 12 Oct 2014 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for camelcase-keys

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 camelcase-keys

Is camelcase-keys safe to use?

Vulert has no vulnerabilities on record for camelcase-keys in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is camelcase-keys's Vulert package health score?

Vulert scores camelcase-keys 80/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 camelcase-keys affected?

No. 10.0.3, 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 camelcase-keys should I use?

10.0.3 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 camelcase-keys have?

0 vulnerabilities are recorded for camelcase-keys in the npm ecosystem: 0 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 camelcase-keys vulnerabilities disclosed?

0 vulnerabilities were recorded for camelcase-keys in the last 12 months. 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 camelcase-keys 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 camelcase-keys for upcoming vulnerabilities?

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