Vulnerability Database · npm · jekyll-for-github-projects · Version
jekyll-for-github-projects 0.2.8
0.2.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: 0.2.11.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 19 Apr 2017
Status deprecated release
Licence ISC
Also known from other sources 0
Newer releases 18
Database updated 22/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
jekyll-for-github-projects 0.2.8 vulnerabilities
1 vulnerability cover jekyll-for-github-projects 0.2.8. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Malicious Package in jekyll-for-github-projects | N/A critical | No fix published | 03 Sep 2020 |
Looking for another version, or everything Vulert holds for jekyll-for-github-projects?
Questions
About jekyll-for-github-projects 0.2.8
Is jekyll-for-github-projects 0.2.8 vulnerable?
Yes. 1 vulnerability in the Vulert database cover jekyll-for-github-projects 0.2.8: 1 critical, 0 high, 0 medium and 0 low. The upgrade Vulert recommends is 0.2.11, and each entry above names the fixed version to move to.
Which version of jekyll-for-github-projects should I use instead of 0.2.8?
0.2.11 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 0.2.8 the latest release of jekyll-for-github-projects?
No. 0.2.8 was published 19 Apr 2017, 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 jekyll-for-github-projects for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the jekyll-for-github-projects version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.