You ship code through GitHub
See what GitHub shows about a real pull request: which revision was approved and which checks ran on the code that merged.
Free · no login · runs in your browser
Try AtlaSent’s free checks on your own work.
Each one answers a single question in your browser. None needs an account, and none uploads what you check.
Want a concrete example first? See when a refund agent should stop, try fictional refund requests and inspect a sample decision log.
Which one first?
Start with the one that matches your work.
You decide who approves production changes
Describe your approval rule and see whether self-approval, a repeated reviewer or an old approval would get through.
You give AI agents tools
Paste an MCP tool list and see which tools could move money, delete data or run code.
You want a quick look at your whole change path
Answer five yes-or-no questions about how production changes are approved and recorded.
All four
What each one needs, and what it can’t tell you.
Change Check
You need: the address of a public GitHub pull request. It reads: the pull request, its reviews, checks and branch rules, directly from GitHub in your browser. It can’t see: bypass rights, approvals outside GitHub, or what was actually deployed.
Approval Tester
You need: your approval rule: how many approvals, how long they last, whether the requester may approve. It runs: AtlaSent’s policy engine in your browser against fixed scenarios. It can’t see: whether production actually follows your rule.
AI Permission Check
You need: an MCP tool list (the JSON a server returns for tools/list). It reads: what each tool says it does. It can’t see: what the tools or their credentials can really do.
Change control self-check
You need: five yes-or-no answers about your change process. You get: a summary of what to verify. It can’t see: anything; it is self-reported.
These are free, educational checks. They are not a security assessment, a certification or an enforcement control, and passing one does not mean a change is authorized. To check one real workflow end to end, see the Production Change Control Audit; to enforce a rule before a deploy runs, start with the developer path.
Also free · no login · in the AtlaSent console
Two more checks for evidence and access.
AtlaSent Proof
Received an AtlaSent evidence package? See who signed it, whether anything in it was changed, and whether it is complete, without trusting our dashboard. It runs in your browser and the file is never uploaded.
Sensitive Access preview
Describe one access grant: who needs what, for how long, and who approves. See which cases would be held, refused or allowed. It is an illustrative preview: nothing is granted, and the draft stays in your browser.
When you want GitHub to stop an unapproved deploy, not just show it, that is the paid product: Production Change Protection.