Security
Read-only on your code.
Devolyn Guard reads pull requests to verify them. It never runs your code and never writes to your repository. Below is the exact permission set GitHub will show you on the install screen — nothing here is a claim you have to take on trust.
Deterministic. No AI reads your code.
Guard analyses changes with parsers and explicit rules. No language model is involved in reaching a verdict, and your code is never used to train one. The same input gives the same verdict, every time — which is what makes a verdict auditable.
Your code is never executed.
Guard parses your code; it does not run it. There is no build step, no test run, no install of your dependencies. Nothing in your repository is executed on our infrastructure.
Nothing is written to your repository.
The App cannot push a commit, change a branch, or alter a repository setting. It has no write access to repository contents, no Administration permission and no Workflows permission. What it does write is its own verdict: a check run, and an optional comment on the pull request.
Blocking a merge stays your decision.
A RED verdict only stops a merge if you have enabled branch protection and marked the Devolyn Guard check as required. Guard can show you whether that protection is on. It cannot turn it on for you — it has no permission to.
GitHub App
Four permissions. That is the whole list.
Two are read-only, and they are the only two that touch your code. The other two exist so Guard can report its result back: a check run, and a comment on the pull request.
| Permission | Access | Why |
|---|---|---|
| Metadata | Read-only | Basic repository information. GitHub requires this for any app. |
| Contents | Read-only | Read the files changed in a pull request, and the repository's file list and structure. |
| Pull requests | Read and write | Read the pull request, and post Guard's comment on it. This writes to the conversation, not to your code. |
| Checks | Read and write | Post the “Devolyn Guard” check run that carries the verdict. |
Events it subscribes to
- pull_request
- check_run
- check_suite
Not requested
Administration, Workflows, and write access to repository contents. Guard cannot change your repository settings, add or edit a workflow, or commit anything — by permission, not by promise.
Uninstall
Remove the App, and your code goes with it.
Uninstalling the GitHub App from your GitHub settings deletes your source code and everything derived from it: file contents, code excerpts, file paths, the code structure, and the repository connection.
One thing survives, and we would rather say so here than bury it: the tamper-evident audit record. It is append-only by design — that is what makes it usable as evidence — so it keeps repository, function and module names, line numbers, verdicts and rule messages. It never contains your file contents, code excerpts, secret values or file paths.
The full detail, including retention and how to make a request, is in the Privacy Policy.
Where it runs
Servers in Germany, isolated per customer.
The hosted service runs on Hetzner infrastructure in Germany, behind Cloudflare. Connections use TLS. Passwords are hashed with argon2id. Each customer’s data is isolated at the application layer and by database row-level security. No system is perfectly secure; if a breach affects your personal data we will notify you and the authorities as the law requires.
Found something, or want detail we have not published? [email protected]