Vulnerability Database · npm · broccoli-closure · Version
broccoli-closure 1.3.0
1.3.0 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.3.1.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 16 Dec 2015
Licence BSD-3-Clause
Also known from other sources 1
Newer releases 4
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
broccoli-closure 1.3.0 vulnerabilities
1 vulnerability cover broccoli-closure 1.3.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2016-10635: Insecure Download of Executable in broccoli-closure | N/A high | 1.3.1 | 18 Feb 2019 |
Looking for another version, or everything Vulert holds for broccoli-closure?
Questions
About broccoli-closure 1.3.0
Is broccoli-closure 1.3.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover broccoli-closure 1.3.0: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.3.1, and each entry above names the fixed version to move to.
Which version of broccoli-closure should I use instead of 1.3.0?
1.3.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.3.0 the latest release of broccoli-closure?
No. 1.3.0 was published 16 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 broccoli-closure for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the broccoli-closure version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.