Scorecard checks whether GitHub Actions workflow tokens follow least privilege: full marks when each workflow sets read-only permissions at the top level and declares any write permission at job level; one point lost when every job defines permissions but the top level does not. It warns, without deducting, on sensitive job-level write permissions (actions, checks, contents, deployments, packages, security-events, statuses), except for recognised packaging and SARIF-upload steps. It cannot see the organisation-wide read-only default setting.
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.