Vulnerability Database · npm · jscover · Version
jscover 0.2.4
0.2.4 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 25 Feb 2013
Licence MIT
Also known from other sources 1
Newer releases 12
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
jscover 0.2.4 vulnerabilities
1 vulnerability cover jscover 0.2.4. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| OS Command Injection in jscover | 9.8 critical | No fix published | 10 Feb 2022 |
Looking for another version, or everything Vulert holds for jscover?
Questions
About jscover 0.2.4
Is jscover 0.2.4 vulnerable?
Yes. 1 vulnerability in the Vulert database cover jscover 0.2.4: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.2.4 the latest release of jscover?
No. 0.2.4 was published 25 Feb 2013, 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 jscover for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the jscover version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.