Securing Critical Projects Working Group
/All repositories
Overview
HEALTH SCORE
Critical*
Partial score (2/3 categories)
14out of 65
Development cadence is the primary crisis signal. Maintainer coverage shows little to offset it. Every health signal is at or near zero. Security & Supply Chain is unavailable, so weights were redistributed.
LIFECYCLE
Active
Consistent commits, responsive maintainers, regular releases, and healthy issue triage.
Health breakdown
Critical*(14/65)
Maintainer availability, known risks and supply chain posture, and whether the project is actively developed or appropriately stable.
Maintainer responsiveness
No PRs or issues were opened in the review window, so response time could not be measured.
Bus factor
Only 1 active maintainer currently has merge rights.
Organization Diversity
Contributors span 12 organizations.
Archived repositories are excluded from Health Score.
Project Achievements
LeaderboardsAbout
A working group focused on identifying, analyzing, and securing critical open source projects that are widely used across the software ecosystem. The group develops strategies, tools, and best practices to improve the security posture of foundational open source software.
First commit
Software value
$121K
Tags
open source security
critical infrastructure
vulnerability management
security best practices
software supply chain
License(s)
Apache-2.0
Links
Data sources
Git
GitHub