Vulnerability Database · npm · npm-programmatic · Version
npm-programmatic 0.0.2
0.0.2 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 23 Jun 2016
Licence ISC
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
npm-programmatic 0.0.2 vulnerabilities
1 vulnerability cover npm-programmatic 0.0.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-7614: Command Injection in npm-programmatic | 9.8 critical | No fix published | 23 Apr 2020 |
Looking for another version, or everything Vulert holds for npm-programmatic?
Questions
About npm-programmatic 0.0.2
Is npm-programmatic 0.0.2 vulnerable?
Yes. 1 vulnerability in the Vulert database cover npm-programmatic 0.0.2: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.0.2 the latest release of npm-programmatic?
No. 0.0.2 was published 23 Jun 2016, 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 npm-programmatic for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the npm-programmatic version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.