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

OpenSSF Best Practices Badge Criteria silver.static_analysis_common_vulnerabilities: static_analysis_common_vulnerabilities (Silver, MUST)

Silver criterion static_analysis_common_vulnerabilities (MUST; group Analysis, Static code analysis). Criterion text: The project MUST use at least one static analysis tool with rules or approaches to look for common vulnerabilities in the analyzed language or environment, if there is at least one FLOSS tool that can implement this criterion in the selected language. This raises the passing criterion of the same name (there SUGGESTED) to MUST at the silver level.

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 Silver 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.