International (open source ecosystem)

OpenSSF Open Source Project Security Baseline (OSPS Baseline)

66 controls. 1 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

66 controls 1 frameworks share controls with it International (open source ecosystem) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

If you runShared controls
NIST SP 800-21837measure it →

Every control

CodeControlAlso in
BASELINEThe OSPS Baseline: what it is0
OSPS-AC-01.01OSPS-AC-01.01 Use MFA for Sensitive Actions1
OSPS-AC-02.01OSPS-AC-02.01 Restrict Collaborator Permissions1
OSPS-AC-03.01OSPS-AC-03.01 Protect the Primary Branch from Accidental Modification1
OSPS-AC-03.02OSPS-AC-03.02 Protect the Primary Branch from Accidental Modification1
OSPS-AC-04.01OSPS-AC-04.01 Enforce Least Privilege on CI/CD Pipelines1
OSPS-AC-04.02OSPS-AC-04.02 Enforce Least Privilege on CI/CD Pipelines1
OSPS-BR-01.01OSPS-BR-01.01 Prevent Untrusted Input When Building & Releasing1
OSPS-BR-01.03OSPS-BR-01.03 Prevent Untrusted Input When Building & Releasing1
OSPS-BR-01.04OSPS-BR-01.04 Prevent Untrusted Input When Building & Releasing1
OSPS-BR-02.01OSPS-BR-02.01 Assign Unique Version Identifiers0
OSPS-BR-02.02OSPS-BR-02.02 Assign Unique Version Identifiers0
OSPS-BR-03.01OSPS-BR-03.01 Use Encrypted Channels for Development & Release Activity0
OSPS-BR-03.02OSPS-BR-03.02 Use Encrypted Channels for Development & Release Activity1
OSPS-BR-04.01OSPS-BR-04.01 Publish Change Log With Release0
OSPS-BR-05.01OSPS-BR-05.01 Use Standardized Dependency Management Tools1
OSPS-BR-06.01OSPS-BR-06.01 Include Signatures and Hashes With Release1
OSPS-BR-07.01OSPS-BR-07.01 Secure Secrets and Credentials1
OSPS-BR-07.02OSPS-BR-07.02 Secure Secrets and Credentials0
OSPS-DO-01.01OSPS-DO-01.01 Publish User Guides for Basic Functionality0
OSPS-DO-02.01OSPS-DO-02.01 Provide Mechanisms for Reporting Defects0
OSPS-DO-03.01OSPS-DO-03.01 Publish Provenance Verification Instructions1
OSPS-DO-03.02OSPS-DO-03.02 Publish Provenance Verification Instructions1
OSPS-DO-04.01OSPS-DO-04.01 Publish Support Scope and Duration0
OSPS-DO-05.01OSPS-DO-05.01 Document Security Update Scope and Duration0
OSPS-DO-06.01OSPS-DO-06.01 Publish Dependency Management Policy1
OSPS-DO-07.01OSPS-DO-07.01 Provide Instructions on How to Build From Source0
OSPS-GV-01.01OSPS-GV-01.01 Publish Project Roles and Responsibilities1
OSPS-GV-01.02OSPS-GV-01.02 Publish Project Roles and Responsibilities1
OSPS-GV-02.01OSPS-GV-02.01 Provide Public Discussion Mechanisms0
OSPS-GV-03.01OSPS-GV-03.01 Publish Contribution Guide0
OSPS-GV-03.02OSPS-GV-03.02 Publish Contribution Guide0
OSPS-GV-04.01OSPS-GV-04.01 Require Formal Review of Permission Grants1
OSPS-LE-01.01OSPS-LE-01.01 Require Code Contributors to Assert Right to Commit0
OSPS-LE-02.01OSPS-LE-02.01 Ensure Project Licenses are Fully Open Source0
OSPS-LE-02.02OSPS-LE-02.02 Ensure Project Licenses are Fully Open Source0
OSPS-LE-03.01OSPS-LE-03.01 Maintain and Release Licenses in a Well Known Location0
OSPS-LE-03.02OSPS-LE-03.02 Maintain and Release Licenses in a Well Known Location0
OSPS-QA-01.01OSPS-QA-01.01 Publish Source Code and Change History0
OSPS-QA-01.02OSPS-QA-01.02 Publish Source Code and Change History1
OSPS-QA-02.01OSPS-QA-02.01 Publish Software Dependencies1
OSPS-QA-02.02OSPS-QA-02.02 Publish Software Dependencies1
OSPS-QA-03.01OSPS-QA-03.01 Address Pass/Fail Checks Before Accepting Changes1
OSPS-QA-04.01OSPS-QA-04.01 Enforce Security Requirements on All Codebases0
OSPS-QA-04.02OSPS-QA-04.02 Enforce Security Requirements on All Codebases0
OSPS-QA-05.01OSPS-QA-05.01 Prevent Executables in the Codebase0
OSPS-QA-05.02OSPS-QA-05.02 Prevent Executables in the Codebase0
OSPS-QA-06.01OSPS-QA-06.01 Use Automated Testing in CI/CD Pipelines0
OSPS-QA-06.02OSPS-QA-06.02 Use Automated Testing in CI/CD Pipelines0
OSPS-QA-06.03OSPS-QA-06.03 Use Automated Testing in CI/CD Pipelines0
OSPS-QA-07.01OSPS-QA-07.01 Require Merge Approvals1
OSPS-SA-01.01OSPS-SA-01.01 Publish Design Descriptions of System Actors and Actions1
OSPS-SA-02.01OSPS-SA-02.01 Publish External Interface Descriptions0
OSPS-SA-03.01OSPS-SA-03.01 Maintain a Project Security Assessment1
OSPS-SA-03.02OSPS-SA-03.02 Maintain a Project Security Assessment1
OSPS-VM-01.01OSPS-VM-01.01 Publish Coordinated Vulnerability Disclosure Policy1
OSPS-VM-02.01OSPS-VM-02.01 Publish Contacts and Process for Reporting Vulnerabilities.1
OSPS-VM-03.01OSPS-VM-03.01 Maintain Private Vulnerability Reporting Process1
OSPS-VM-04.01OSPS-VM-04.01 Publish Discovered Vulnerabilities1
OSPS-VM-04.02OSPS-VM-04.02 Publish Discovered Vulnerabilities1
OSPS-VM-05.01OSPS-VM-05.01 Publish and Enforce a Dependency Remediation Policy1
OSPS-VM-05.02OSPS-VM-05.02 Publish and Enforce a Dependency Remediation Policy1
OSPS-VM-05.03OSPS-VM-05.03 Publish and Enforce a Dependency Remediation Policy1
OSPS-VM-06.01OSPS-VM-06.01 Publish and Enforce an Application Security Testing Policy1
OSPS-VM-06.02OSPS-VM-06.02 Publish and Enforce an Application Security Testing Policy1
STATUSStatus: v2026.08.28 is current; retired requirement; mappings the Baseline publishes0

Tell me when OpenSSF Open Source Project Security Baseline (OSPS Baseline) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for OpenSSF Open Source Project Security Baseline (OSPS Baseline), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition