Vulnerability Database · npm · decamelize · Version
decamelize 1.1.1
1.1.1 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 29 Oct 2015
Licence MIT
Also known from other sources 1
Newer releases 16
Database updated 23/Oct/2026
Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version
decamelize 1.1.1 vulnerabilities
1 vulnerability cover decamelize 1.1.1. Open the full list 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 |
Looking for another version, or everything Vulert holds for decamelize?
Questions
About decamelize 1.1.1
Is decamelize 1.1.1 vulnerable?
Yes. 1 vulnerability in the Vulert database cover decamelize 1.1.1: 0 critical, 1 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 1.1.1 the latest release of decamelize?
No. 1.1.1 was published 29 Oct 2015, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.