Scorecard checks the assets of recent releases (up to the last five with assets, ignoring automatic source-only releases) for signature files (.minisig, .asc, .sig, .sign, .sigstore, .sigstore.json) and for SLSA provenance (.intoto.jsonl). A signature on each release scores 8; provenance on each release scores 10. The check does not verify the signatures.
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.