A security check on every client project
For agencies and software houses of five to twenty developers who build for clients with Copilot, Cursor or Claude.
Sooner or later a client asks two things: what checks every change to their code goes through, and where that code is sent. MagAudit gives you a short answer to both. It is a GitHub App that runs one security check on each pull request, and it reads the code on a single server in Finland without sending it to an AI model or to anyone else.
Free on public repositories · 14 days free on private ones · no card
What it finds in code written with an assistant
- A service key that ends up in the browser. A key with a
NEXT_PUBLIC_orVITE_prefix is shipped to every visitor. We looked for it in 63 real pull requests and found it zero times; in the existing code of 8 real repositories it was in seven. It is written once, the day the project starts, so we read the existing code when you install and not only the next change. How we measured it. - A credential committed to the repository, with the line and the fix in the pull request comment.
- A dependency published a few days ago that almost nobody uses, which is what a package registered by an attacker looks like before any advisory exists.
- SQL built by interpolation, insecure deserialization, model output rendered as raw HTML, and risky settings in Dockerfiles, GitHub Actions workflows, Terraform and Kubernetes files.
The first report arrives about a minute after you install. From then on the check fails when it finds something serious, so it blocks the merge once you mark it as required in your branch protection.
What you can tell your client
| They ask | You answer |
|---|---|
| Where is our code sent? | To one server in Finland. It is read in memory, never written to disk and never sent to an AI model or a third party. Only package names and versions leave, towards the package registries. |
| What is stored? | No code. The repository name, the pull request number and the number of findings, until the App is uninstalled. |
| Who else processes it? | Listed one by one on the trust page, which is written for vendor reviews. |
| Is the vendor certified? | No SOC 2 or ISO 27001 yet. We are a small company and we say so; the trust page explains what we do instead. |
| How often is the tool wrong? | We publish it, with every correction: our error record. |
What it costs
One flat price for the whole organisation, by number of private repositories: €29 a month for up to 5, €69 for up to 15 and €149 for up to 40. Public repositories are free. Nobody counts how many people commit.
For comparison, GitHub charges per active committer on private repositories: $19 a month for Secret Protection and $30 for Code Security. A team of ten pays around $490 a month. In CodeRabbit the security review of every pull request is only in the Advanced plan, at $72 per developer per month. MagAudit does not replace your reviewer: it adds the security check next to it. Full pricing.
The App is installed in the GitHub organisation that owns the repositories, and the plan belongs to that organisation. If a client keeps the code in their own organisation, it is installed there.
How to try it without committing to anything
- Install it and choose Only select repositories. Pick one project.
- Read the first report, about a minute later, on the code that is already there.
- Open a pull request and see the check and the comment.
- If it is not for you, uninstall it. What we stored about the installation is deleted.
Questions before installing? Write to contact@magsolutionsai.com and the person who built it answers.
Last reviewed: 11 November 2026. Competitor prices are the ones published on their own pricing pages on that date.