OpenSSF Scorecard
OpenSSF Scorecard's twenty automated checks of an open source repository's security practices, each scored 0 to 10 with a risk level: from dangerous CI workflow patterns and token permissions to branch protection, code review, pinned dependencies, signed releases, SBOMs and known vulnerabilities. Heuristic signals, not requirements; read against the v5.5.0 check documentation.
OpenSSF Scorecard is a compliance framework from International (open source ecosystem) with 4 domains and 20 controls that map to 132 other frameworks. The largest domains are High-risk checks – OpenSSF Scorecard (8 controls), Medium-risk checks – OpenSSF Scorecard (6 controls), Low-risk checks – OpenSSF Scorecard (4 controls). Every control below carries what it requires and what an assessor expects to see.
Framework summaries on this platform are interpretations grounded in the published source, for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (4)
Critical-risk checks – OpenSSF Scorecard
| Code | Title |
|---|---|
| openssf-scorecard::Dangerous-Workflow | Dangerous-Workflow check |
| openssf-scorecard::Webhooks | Webhooks check |
High-risk checks – OpenSSF Scorecard
| Code | Title |
|---|---|
| openssf-scorecard::Binary-Artifacts | Binary-Artifacts check |
| openssf-scorecard::Branch-Protection | Branch-Protection check |
| openssf-scorecard::Code-Review | Code-Review check |
| openssf-scorecard::Dependency-Update-Tool | Dependency-Update-Tool check |
| openssf-scorecard::Maintained | Maintained check |
| openssf-scorecard::Signed-Releases | Signed-Releases check |
| openssf-scorecard::Token-Permissions | Token-Permissions check |
| openssf-scorecard::Vulnerabilities | Vulnerabilities check |
Low-risk checks – OpenSSF Scorecard
| Code | Title |
|---|---|
| openssf-scorecard::CI-Tests | CI-Tests check |
| openssf-scorecard::CII-Best-Practices | CII-Best-Practices check |
| openssf-scorecard::Contributors | Contributors check |
| openssf-scorecard::License | License check |
Medium-risk checks – OpenSSF Scorecard
| Code | Title |
|---|---|
| openssf-scorecard::Fuzzing | Fuzzing check |
| openssf-scorecard::Packaging | Packaging check |
| openssf-scorecard::Pinned-Dependencies | Pinned-Dependencies check |
| openssf-scorecard::SAST | SAST check |
| openssf-scorecard::SBOM | SBOM check |
| openssf-scorecard::Security-Policy | Security-Policy check |
Your Compliance Coverage
If you comply with OpenSSF Scorecard, you already cover:
NIST SP 800-218
43%
12 controls mapped
Compare →OWASP MASVS
25%
7 controls mapped
Compare →OWASP ASVS
25%
7 controls mapped
Compare →+ 129 more: ISO/SAE 21434 (25%), ISO/IEC 27043:2015 (25%)
See all 132 mapped frameworks ↓Maps to 132 other frameworks
Coverage is not the same as your position
This page shows what OpenSSF Scorecard overlaps with in general. Where your organisation actually stands, against the standard you are going for and the certifications you already hold, is a different question. Same graph and the same recorded refutations, scoped to you rather than to a pair.
The Compliance Position Diagnostic, $5,000 fixed, ten business daysWhat is OpenSSF Scorecard and who does it apply to?
OpenSSF Scorecard is a compliance framework from International (open source ecosystem) with 4 domains and 20 controls. OpenSSF Scorecard's twenty automated checks of an open source repository's security practices, each scored 0 to 10 with a risk level: from dangerous CI workflow patterns and token permissions to branch protection, code review, pinned dependencies, signed releases, SBOMs and known vulnerabilities. Heuristic signals, not requirements; read against the v5.5.0 check documentation. It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
What does OpenSSF Scorecard actually require?
OpenSSF Scorecard has 20 controls organised across 4 domains. The largest domains are High-risk checks – OpenSSF Scorecard (8 controls), Medium-risk checks – OpenSSF Scorecard (6 controls), Low-risk checks – OpenSSF Scorecard (4 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
If I already comply with another framework, how much of OpenSSF Scorecard do I already cover?
OpenSSF Scorecard maps to 132 other compliance frameworks. The top mapping partners are NIST SP 800-218 (43% coverage), OWASP MASVS (25% coverage), OWASP ASVS (25% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I implement OpenSSF Scorecard?
Start your OpenSSF Scorecard compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about OpenSSF Scorecard requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 20 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 1,121 frameworks.
Get Started Free →Free forever, no credit card required