OSPS-DO-06 Publish Dependency Management Policy (maturity levels 2, 3). Requirement: When the project has made a release, the project documentation MUST include a description of how the project selects, obtains, and tracks its dependencies. Objective of the control: Provide information about how the project selects, obtains, and tracks third-party components that are required for the software to function. Recommendation: It is recommended to publish this information alongside the project's technical & design documentation on a publicly viewable resource such as the source code repository, project website, or other channel.
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.