Vulnerability Database · npm · git-dummy-commit · Version
git-dummy-commit 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 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 26 Dec 2015
Licence MIT
Also known from other sources 1
Newer releases 6
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
git-dummy-commit 1.1.1 vulnerabilities
1 vulnerability cover git-dummy-commit 1.1.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2018-3785: Command Injection in git-dummy-commit | 9.8 critical | No fix published | 21 Aug 2018 |
Looking for another version, or everything Vulert holds for git-dummy-commit?
Questions
About git-dummy-commit 1.1.1
Is git-dummy-commit 1.1.1 vulnerable?
Yes. 1 vulnerability in the Vulert database cover git-dummy-commit 1.1.1: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 1.1.1 the latest release of git-dummy-commit?
No. 1.1.1 was published 26 Dec 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 git-dummy-commit for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the git-dummy-commit version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.