What we access, and what we keep

Connecting your repository lets us verify it continuously. Here is exactly what that means, in plain terms.

Read-only, and GitHub enforces it

The app can only read. GitHub shows you the exact permissions before you install and blocks anything else at their level, so you are not relying on our word. You choose which repositories it can see, and nothing outside those.

Analyzed in a throwaway sandbox

When we scan, we pull a copy of the code into an isolated environment, run the analysis there, and destroy that environment when it finishes. The copy does not persist.

We keep the results, not your code

What we store is the output of the analysis: the list of tools the server exposes, its capability surface, the findings, the grade, and a fingerprint (hash) used to detect changes. We do not store your source code.

Nothing is retained or resold

We do not keep a copy of your repository, and we do not share the internals of a private repository. Private stays private; what we publish is the verification result.

You are in control

You pick the repositories, you pick the access level, and you can uninstall in one click at any time. Removing the app revokes our access immediately and takes down the badge.

Do not trust us, read the scanner

The analysis is meant to be inspectable. You can review what the scanner does so you can confirm for yourself that it reads to verify and nothing more.

Two levels, your choice

Monitor

Metadata and dependency information only. No source access. We watch for new releases and dependency vulnerabilities and re-verify when you ship. Safe for any repository.

Verify

Adds read access to file contents, used to analyze the source directly. Only needed for private repositories, since public source we can already read. Optional, and you can start with Monitor.

Questions before you connect? Email support@m8ven.ai.