OpenSSF Best Practices Badge Criteria
Passing level: Analysis – OpenSSF Best Practices Badge Criteria

OpenSSF Best Practices Badge Criteria passing.static_analysis: static_analysis (Passing, MUST)

Passing criterion static_analysis (MUST; group Analysis, Static code analysis). Criterion text: At least one static code analysis tool (beyond compiler warnings and "safe" language modes) MUST be applied to any proposed major production release of the software before its release, if there is at least one FLOSS tool that implements this criterion in the selected language.

Maintained by Gerard Blokdyk

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 Passing level: Analysis – OpenSSF Best Practices Badge Criteria

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.