OSPO Hugo Theme

OSPO Hugo Theme

63

A theme for the Hugo CMS to launch an OSPO

Documentation
70
License
75
Best practices
26
Security
45
Legal
100
70
Documentation
These checks highlight opportunities to improve the documentation of your project.
failed
Adopters
List of organizations using this project in production or at stages of testing
Governance
Document that explains how the governance and committer process works in the repository
Maintainers
The maintainers file contains a list of the current maintainers for the repository
Roadmap
Defines the high-level overview of the project’s goals and deliverables
passed (5)
Show Hide
Changelog
A curated, chronologically ordered list of notable changes for each version
Code of conduct
Adopt a code of conduct to define community standards and outline procedures for handling abuse
Contributing
A contributing file provides potential contributors with a short guide to how they can help
Readme
The readme file introduces and explains a project
Website
A url that users can visit to learn more about your project
75
License
These checks ensure the project has compliant licensing.
failed
License scanning
Automatically identify, manage and address open source licensing issues
passed (2)
Show Hide
Compliance
The license is approved within the organization
License
The LICENSE file contains the repository license
26
Best practices
These checks evaluate recommended practices for the project.
failed
Messaging support available
A messaging platform allows to build up the community for the project
Contributor License Agreement
Defines the terms under which intellectual property has been contributed to a project
GitHub Discussions
GitHub Discussions enable better collaboration on the project
Issue Template
An Issue template helps with filing bugs on the project
OpenSSF Badge
The OpenSSF Best Practices badge shows that the project follows best practices
Scorecard Badge
Scorecard assesses open source projects for security risks through automated checks
Pull Request Template
A Pull Request template speeds up the approval process
passed (2)
Show Hide
Developer Certificate of Origin
Mechanism for contributors to certify that they wrote or have the right to submit the code
Recent Release
The project should have released at least one version in the last year
45
Security
These checks ensure that your project is following security practices.
failed
Dependency Policy
Project should provide a dependencies policy that describes how dependencies are consumed and updated
Software Bill of Materials
List of components in a piece of software, including licenses, versions, etc.
Signed Release
This check tries to determine if the project cryptographically signs release artifacts
Token Permissions
This check determines whether the project’s automated workflow tokens are set to read-only by default
passed (6)
Show Hide
Binary artifacts
This check determines whether the project has generated executable artifacts in the source repository
Code Review
This check determines whether the project requires code review before pull requests are merged
Dangerous Workflow
This check determines whether the project’s GitHub Action workflows has dangerous code patterns
Dependency Update Tool
This check tries to determine if the project uses a dependency update tool
Maintained
This check determines whether the project is actively maintained
Security Policy
Clearly documented security processes explaining how to report security issues
100
Legal
These checks ensure that your project is compliant with the legal guidelines.
failed
Trademark
A trademark should be applied to protect intellectual property