Vulnerability Database · npm · frames-compiler · Version
frames-compiler 1.0.8
1.0.8 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.0.8.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 17 Jun 2016
Status latest release
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
frames-compiler 1.0.8 vulnerabilities
1 vulnerability cover frames-compiler 1.0.8. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2016-10649: frames-compiler - Insecure Download of Executable | 8.1 high | No fix published | 01 Sep 2020 |
Looking for another version, or everything Vulert holds for frames-compiler?
Questions
About frames-compiler 1.0.8
Is frames-compiler 1.0.8 vulnerable?
Yes. 1 vulnerability in the Vulert database cover frames-compiler 1.0.8: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.0.8, and each entry above names the fixed version to move to.
Which version of frames-compiler should I use instead of 1.0.8?
1.0.8 is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.0.8 the latest release of frames-compiler?
Yes. 1.0.8 is the current release, published 17 Jun 2016. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor frames-compiler for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the frames-compiler version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.