Project Summary
clr-boot-manager exists to enable the correct maintenance of vendor kernels and appropriate garbage collection tactics over the course of upgrades. The implementation provides the means to enable correct cohabitation on a shared boot directory, such as the EFI System Partition for UEFI-booting operating systems.
Most importantly, clr-boot-manager provides a simple mechanism to provide kernel updates, with the ability for users to rollback to an older kernel should the new update be problematic. This is achieved through the use of strict namespace policies, permanent source paths, and clr-boot-manager's own internal logic, without the need for "meta packages" or undue complexity on the distribution side.
In a Nutshell, clr-boot-manager...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a small development team
with increasing Y-O-Y commits -
...
took an estimated 3 years of effort (COCOMO model)
starting with its first commit in March, 2016
ending with its most recent commit 8 months ago
Quick Reference
GNU Lesser General Public License 2.1
Permitted
Forbidden
Required
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Vulnerability Exposure Index
Did You Know...
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
anyone with an Open Hub account can update a project's tags
-
...
there are over 3,000 projects on the Open Hub with security vulnerabilities reported against them
-
...
you can embed statistics from Open Hub on your site
30 Day SummaryMay 19 2025 — Jun 18 2025
|
12 Month SummaryJun 18 2024 — Jun 18 2025
|
