Was this change really approved?
Check a repository or pull request
Your browser asks GitHub's public API directly, with no login. AtlaSent does not receive the address or the result. If you accept analytics cookies, we count that a check finished, never which repository. A repository check uses 11 to 13 of the roughly 60 public GitHub lookups your network gets each hour.
Were recent merges approved?
Needs attention
Pull requests, newest merge first
How to have GitHub enforce this
What this free check can’t see, and AtlaSent can
This free check reads only GitHub. AtlaSent works at the moment of deploy: the approval is bound to the repository, commit and environment, so changed work needs a new decision before it can deploy, and the decision, the check at execution and what actually ran are kept as signed records your auditor can verify offline. How AtlaSent checks the deploy →
Check pull requests where you review them
Drag this button to your browser’s bookmarks bar. Then, on any GitHub pull request page, click it to open this check for that pull request.
It reads only the address of the page you are on and opens this page in a new tab. Nothing is installed.
What GitHub shows about this change
Needs attention
What this free check can’t see, and AtlaSent can
This free check reads only GitHub. AtlaSent works at the moment of deploy: the approval is bound to the repository, commit and environment, so changed work needs a new decision before it can deploy, and the decision, the check at execution and what actually ran are kept as signed records your auditor can verify offline. How AtlaSent checks the deploy →
Was this useful?
What was missing?
What you can do next
Get an evidence-based answer
The fixed-scope $750 Production Change Control Audit reviews one workflow end to end, including what GitHub cannot show: bypass routes, out-of-band approvals and what actually ran. It is not a certification or an installation of enforcement.
Ask the five questions
A two-minute self-check on approvals, independence and execution evidence to discuss with your team.
Gate the deploy itself
Add one AtlaSent step before your deploy so it runs only after the exact change is approved.
Other free checks: Approval Tester · AI Permission Check · Change control self-check · all free tools