VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

decamelize: vulnerability history, versions and safety

decamelize is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 2 releases, first recorded in Jul 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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 decamelize vulnerabilities

Vulert verdict on decamelize 7.0.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 7.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Jul 2018 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 10 packages i
  • Stars 245 i
  • OpenSSF scorecard 3/10 i
  • Last release this month 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 decamelize, 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
7.0.0 13 Oct 2026 none MIT — Details →
6.0.1 19 Aug 2025 none MIT — Details →
6.0.0 01 Oct 2021 none MIT — Details →
5.0.1 29 Sep 2021 none MIT — Details →
5.0.0 11 Jan 2021 none MIT — Details →
4.0.0 26 Jan 2020 none MIT — Details →
3.2.0 05 Apr 2019 none MIT — Details →
3.1.1 22 Mar 2019 none MIT — Details →
3.1.0 21 Mar 2019 none MIT — Details →
3.0.0 06 Mar 2019 none MIT — Details →
2.0.0 08 Jan 2018 none MIT — Details →
1.2.0 05 Mar 2016 none MIT — Details →
1.1.2 23 Dec 2015 none MIT — Details →
1.1.1 29 Oct 2015 H1 MIT Yes Details →
1.1.0 25 Oct 2015 H1 MIT Yes Details →
1.0.0 24 Jan 2015 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1

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

03 Vulnerabilities

Recorded vulnerabilities for decamelize

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16023: Regular Expression Denial of Service in decamelize 7.5 high 1.1.2 24 Jul 2018

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 decamelize

Is decamelize safe to use?

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

Vulert scores decamelize 72/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 decamelize affected?

No. 7.0.0, 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.

How many vulnerabilities does decamelize have?

1 vulnerability is recorded for decamelize in the npm ecosystem: 0 critical, 1 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 decamelize vulnerabilities disclosed?

0 vulnerabilities were recorded for decamelize in the last 12 months, and the oldest entry in this database dates to 24 Jul 2018. 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 decamelize 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 decamelize for upcoming vulnerabilities?

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