OpenSSF Scorecard
High-risk checks – OpenSSF Scorecard

OpenSSF Scorecard Code-Review: Code-Review check

Scorecard checks whether recent changes (about the last 30 commits) were reviewed by a human before merge: an approval on GitHub or GitLab, a merger different from the committer, Prow lgtm or approved labels, or Gerrit Reviewed-on and Reviewed-by trailers. Scoring is levelled: three points are lost if any bot-originated change is unreviewed, seven if one human change is unreviewed and a further three if several are. Reviews by bots, including AI or machine-learning bots, do not count. If recent changes are bot-only the result is inconclusive.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-218 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in High-risk checks – OpenSSF Scorecard

Query this from an agent

The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.