OSPS-QA-01 Publish Source Code and Change History (maturity levels 1, 2, 3). Requirement: The version control system MUST contain a publicly readable record of all changes made, who made the changes, and when the changes were made. Objective of the control: Enable users to access and review the project's source code and history, promoting transparency and collaboration within the project community. Recommendation: Use a common VCS such as GitHub, GitLab, or Bitbucket to maintain a publicly readable commit history. Avoid squashing or rewriting commits in a way that would obscure the author of any commits.
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.
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.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.