Security Checks
Last updated
Was this helpful?
Last updated
Was this helpful?
This check determines whether the project has generated executable (binary) artifacts in the source repository. For more details, see the
ID: code_review
This check determines whether the project requires code review before pull requests (merge requests) are merged. For more details, see the
ID: dangerous_workflow
This check determines whether the project’s GitHub Action workflows has dangerous code patterns. For more details, see the .
ID: dependency_update_tool
This check tries to determine if the project uses a dependency update tool, specifically or . For more details, see the
ID: maintained
This check determines whether the project is actively maintained. For more details, see the
ID: sbom
List of components in a piece of software, including licenses, versions, etc.
This check passes if:
The latest release on Github includes an asset which name contains sbom. Regexps used:
The repository’s README
file contains a SBOM section that explains where they are published to, format used, etc. Regexps used to locate the title header:
ID: security_policy
Documented security processes explaining how to report security issues to the project.
This check passes if:
A security policy file is found in the repository. Globs used:
A security policy reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
ID: signed_releases
ID: token_permissions
A security policy file is found in the
This check tries to determine if the project cryptographically signs release artifacts. For more details, see the
This check determines whether the project’s automated workflows tokens are set to read-only by default. For more details, see the