| Badge Type | Qualification Criteria | Monitoring Method | Monitoring Frequency | Requirement for Stages | Penalty for Non-Compliance | Notes |
|---|---|---|---|---|---|---|
| Legal | Project Badging Proposal | GitHub Action | Continuous | All | Move to "deprecated"? | |
| Diversity/Decentralized | Project Badging Proposal | GitHub Action? | Continuous | All | ||
| Release | Project Badging Proposal | |||||
| Testing | Project Badging Proposal | |||||
| Documentation | Project Badging Proposal | |||||
| Alignment | Project Badging Proposal | |||||
| Infrastructure | Project Badging Proposal | |||||
| CII | Project Badging Proposal | |||||
| Security? | https://github.com/arsulegai/tsc/blob/security-gov/governing-documents/security.md (PR under review) | |||||
| Reuse/Unique? | Should reuse components from other Hyperledger projects as needed and not reinvent the wheel | |||||
| CI/CD | Best Practices for Automated Pipelines | |||||
| Automation/Usability? | Can users easily launch and test the software using automated scripts or do they have to jump through hoops to get started? | |||||
| OpenSSF Best Practices? | https://github.com/hyperledger/toc/blob/gh-pages/guidelines/project-best-practices.md | |||||
| Conformity? | Does the look and feel of the repo structure and the documentation match that of other projects (according to Hyperledger's recommended practices)? This may overlap with "documentation". Need suggestions from documentation task force. | |||||
| Responsiveness/Engagement? | Are maintainers engaging with the community and responding reasonably promptly to questions and solicitations for involvement? Need suggestions from onboarding task force. The number of summer mentees may also factor into this. | |||||
| Production? | Is the software currently being used in at least one production-grade system outside of Hyperledger (publicly verifiable or certified by third party consumer)? |
Overview
Content Tools
Activity