no binaries found in the repo

Determines if the project has generated executable (binary) artifacts in the source repository.

no dangerous workflow patterns detected

Determines if the project's GitHub Action workflows avoid dangerous patterns.

30 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10

Determines if the project is "actively maintained".

0 existing vulnerabilities detected

Determines if the project has open, known unfixed vulnerabilities.

branch protection not enabled on development/release branches

Determines if the default and release branches are protected with GitHub's branch protection settings.

no effort to earn an OpenSSF best practices badge detected

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Found 1/30 approved changesets -- score normalized to 0

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

project is not fuzzed

Determines if the project uses fuzzing.

license file not detected

Determines if the project has defined a license.

dependency not pinned by hash detected -- score normalized to 0

Determines if the project has declared and pinned the dependencies of its build process.

SAST tool is not run on all commits -- score normalized to 0

Determines if the project uses static code analysis.

security policy file not detected

Determines if the project has published a security policy.

Project has not signed or included provenance with any releases.

Determines if the project cryptographically signs release artifacts.

detected GitHub workflow tokens with excessive permissions

Determines if the project's workflows follow the principle of least privilege.

packaging workflow not detected

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.