no binaries found in the repo

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

license file detected

Determines if the project has defined a license.

9 commit(s) and 9 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.

Found 15/29 approved changesets -- score normalized to 5

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

no effort to earn an OpenSSF best practices badge detected

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

project is not fuzzed

Determines if the project uses fuzzing.

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.

internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration

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

no workflows found

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

packaging workflow not detected

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

no dependencies found

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

No tokens found

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