Review GitHub Actions GITHUB_TOKEN permissions
How to inspect and reduce GitHub Actions GITHUB_TOKEN write permissions, including job scopes and the special id-token: write permission.
Read note →Qira Proof / field notes
Focused engineering references on configurations we can actually observe, how to review them, and what the evidence does not prove.
How to inspect and reduce GitHub Actions GITHUB_TOKEN write permissions, including job scopes and the special id-token: write permission.
Read note →A practical review of GitHub Actions action reference pinning, SHA digests, dependency lockfiles and supply-chain provenance limitations.
Read note →Why ssh-keyscan alone is not independent host authentication and how to review a secure known_hosts trust bootstrap in CI.
Read note →How to find fail-open security checks and publish paths that are not bound to verified merges, with a real pinned LOLM example.
Read note →The guides explain the inspection principles used in Qira Proof's bounded configuration assessment. They are not intended as proof that any particular repository is vulnerable.
Our public LOLM case study includes direct line citations and a clear distinction between scanner-corroborated YAML and manually reviewed Python control flow. The methodology page explains the paid-review boundaries.
See the source. A pinned, first-party LOLM case shows what we actually examined. See the format. The synthetic sample shows how an action plan is structured. See the scope. The $299 page explains what an authorized buyer receives.