Skip to content
GitHub App · Free on public repos

Every pull request, triaged at a glance — including the ones your AI agents open.

GitAlert is an independent GitHub check. On each PR it shows who opened it (AI agent, bot or person), what it touches (CI, secrets, new dependencies) and how big it is, then posts one neutral label. It never blocks a merge and never comments.

Looks solid Worth a closer look Likely needs attention
Works with GitHub App GitLab and Bitbucket planned

Create a free account

No password to set. Free on public repositories.

Continue with GitHub

GitAlert is a GitHub App, so use the GitHub account that owns your repos.

Other sign-in options

Triage currently needs a GitHub account. Use one of these if your GitAlert account was created with it.

By continuing, you accept our Terms of use.

Beta GitAlert is in beta — your feedback shapes what we build next.

What reviewers see

One check beside your CI. No comments, no red ✗.

GitAlert Triage sits in the pull request's checks list, next to your build and tests. It says who opened the PR and how big it is, lists each new package with its registry, and names the sensitive files it changes. It never fails the build.

Retry failed requests in the HTTP client #482
devin/http-retry main
Open
build 2m 14s
unit-tests 1m 03s
GitAlert Triage Likely needs attention Details
Opened by:
AI agent (devin-ai-integration[bot])
Size:
6 files, +212 −40
Suspect new dependency:
reqests (pypi) — not found on registry
Sensitive file:
.github/workflows/ci.yml
Neutral check, informational only. You and your reviewers decide what merges.

Illustrative example. GitAlert never fails your build or comments on your PR.

How it works

Install once. Every PR gets a label.

Sign in with GitHub, choose repositories, and GitAlert checks each pull request as it opens or updates. No pipeline to configure, no script to write.

PR opened Triaged
  1. Install the GitHub App

    Sign in with GitHub and add GitAlert to the repositories you choose. It reads your pull requests and posts its own neutral check. It never pushes commits, changes your branches, merges or comments.

  2. Someone opens a pull request

    Whenever a teammate or an AI coding agent opens or updates a PR, GitAlert reads the diff automatically, every time.

  3. Read one label

    The check shows who opened the PR, how big it is, the new dependencies it adds and the sensitive files it changes. Then one of three labels. You stay in charge of the merge.

    Looks solid Worth a closer look Likely needs attention
pull request #517 · checks
GitAlert Triage Looks solid
Opened by:
human (maria-dev)
Size:
2 files, +18 −3
Flags:
none of GitAlert's checks fired

Neutral check · never blocks the merge · illustrative example

What it surfaces

Four things to know before you review a PR

Most pull requests are fine. GitAlert reads every diff the same way, every time, so your reviewers know where to look first.

Who opened it

An AI agent, an automation bot or a person, with the evidence: a known agent account, or a "Generated with…" line in the PR.

What it touches

CI and workflow files, secrets and keys, container and infrastructure config. A PR that edits one gets at least "Worth a closer look".

New dependencies

Packages added to a manifest such as requirements.txt, pyproject.toml, package.json, composer.json, Cargo.toml, go.mod or Gemfile, up to 25 per PR, with any name that isn't on its registry flagged.

How big it is

Files changed and lines added and removed, so a 2,000-line agent PR never looks like a one-line fix.

It also points out test edits worth a second look, such as a newly skipped test or a weakened or always-true assertion. Those flags name the test file, and the exact line when a single line is responsible. Dependency flags name the package and its registry.

Triage, not a verdict

One label to help you prioritise, never a pass/fail or a red ✗. The check shows its confidence so you can weigh it.

Same diff, same label

Fixed rules, not a model's opinion. The same change gets the same result every time.

GitHub today

GitAlert is a GitHub App. GitLab and Bitbucket are on the roadmap.

Free on public repos

Up to 150 PR checks a month, no credit card. A PR is checked when it opens and again on each new commit, and open PRs are checked when you install or add repositories. Paid plans add private repositories and higher limits.

Try it on your next pull request

Install GitAlert on a public repository, then open or update a pull request. The triage check appears on the PR — no credit card, and no comments on your PRs.

FAQ

Frequently asked questions

Everything you need to know before installing GitAlert.

Still have a question? Contact us.

What does GitAlert surface on a pull request?

On every pull request, GitAlert posts one neutral GitHub check, GitAlert Triage. It shows who opened the PR (an AI agent, an automation bot or a person, with the evidence), what it touches (CI and workflow files, secrets and keys, container and infrastructure config), the new dependencies it adds (flagging any name that is not on its registry) and how big it is (files changed, lines added and removed). Then it gives one label: Looks solid, Worth a closer look, or Likely needs attention. It also points out test edits worth a second look, such as a newly skipped test or a weakened assertion; those flags name the test file, and the exact line when a single line is responsible. Dependency flags name the package and its registry.

Does GitAlert block merges or comment on pull requests?

No. The check's result is always neutral, which GitHub never treats as a failure, so it never shows a red ✗ and cannot stop a merge. GitAlert does not comment on pull requests, push commits, change branches or merge anything. You and your reviewers decide what ships.

Which AI coding agents does GitAlert recognise?

GitAlert recognises the accounts coding agents open pull requests from, including GitHub Copilot's coding agent, Devin, Cursor, OpenAI Codex, Google Jules, Claude, OpenHands, Sweep, Aider, Factory, Codegen and Gemini Code Assist. It also recognises a pull request whose description credits an agent or a model, such as a "Generated with Claude Code" line or a "Co-authored-by:" line naming an agent, which covers agents that push through your own account. Dependency bots such as Dependabot and Renovate count as automation bots, not AI agents.

How does GitAlert tell an AI agent's pull request from a person's?

With fixed rules applied to evidence on the pull request. A PR opened by a known agent account, such as Devin's or Copilot's, is an AI agent PR. A PR from a person's account counts as an AI agent PR only when its title or description carries an explicit marker: a "Generated with" line naming a known agent, such as Claude Code, Cursor or Devin, a "Co-authored-by:" line naming an agent, or a statement that a named model or a local LLM generated it. Known dependency and CI bots count as automation bots unless the pull request says an AI agent or a model wrote it. Any other bot account counts as an automation bot unless its title or the start of its description names one of Copilot, Devin, Cursor, Codex, OpenHands, Aider, Sweep, Codegen, Factory Droid or Ellipsis. Any other account counts as a person, and a deleted account as unknown. The check shows the evidence it used, so you can see why.

Which files does GitAlert treat as sensitive?

A fixed set: secret and key files (.env and .secrets files, .npmrc, .pypirc, .netrc, id_rsa and id_ed25519, credentials and secrets.yml files, .pem, .p12, .pfx, .jks, .keystore, .ppk, .asc and .gpg files, and .key files in certificate or key folders), CI config (.github/workflows, .github/actions, action.yml, .circleci, .gitlab-ci.yml, Jenkinsfile, .travis.yml and azure-pipelines.yml), container files (Dockerfile, Containerfile and docker-compose.yml) and Terraform files (.tf and .tfvars). A pull request that changes one lists it under sensitive file touches and gets at least "Worth a closer look". It never blocks the merge.

How does GitAlert check new dependencies?

When a pull request adds a package to a requirements file (requirements.txt, requirements-dev.txt, requirements.in or a file in a requirements/ folder), pyproject.toml, setup.py, setup.cfg, package.json, composer.json, Cargo.toml, go.mod or a Gemfile, GitAlert lists it and checks that the name exists on its public registry: PyPI, npm, Packagist, crates.io, the Go module proxy or RubyGems. Only the package name is sent, never your code. Up to 25 new packages are checked per pull request; past that, the check says the scan was cut short. A name the registry does not know is flagged as a suspect new dependency and the PR gets "Likely needs attention", because AI agents sometimes invent package names and attackers register those names to slip malware into builds ("slopsquatting").

What data does GitAlert read and store?

GitAlert reads pull-request metadata and the PR diff. The diff is analysed in memory and is not stored, and neither is your source code. It keeps the installation, repository and pull-request metadata (such as the number, title, description, author, branches and commit ids) and the verdict: the label, the confidence and the findings behind it. GitHub access tokens are minted on demand and never stored in our database. On the free plan GitAlert never runs your code; on paid plans it may build a public repository and run its existing tests in an isolated, single-use sandbox that receives no secrets. The Privacy & security page has the full detail.

What's free, and what are the limits?

Triage on public repositories is free, with no credit card: up to 150 pull-request checks a month, run one at a time. A check runs when a pull request is opened and again each time new commits are pushed to it, so a PR opened and then updated twice uses three checks. It also runs when a pull request is reopened or marked ready for review, when you press Re-run, for up to 25 open pull requests each time you install GitAlert or add repositories, and for up to 25 that a plan limit held back when you upgrade. The same commit costs at most one check in any 6 hours, so reopening a pull request or pressing Re-run soon after a check costs nothing. When the month's checks run out, pull requests get a neutral "Couldn't verify" check until the next month. Private repositories need a paid plan; on the free plan their pull requests get that same neutral check instead of a label. Team adds private repositories, with up to 1,000 checks a month, 3 at a time; Scale raises that to 10,000 a month, 10 at a time. Enterprise has custom limits on an annual contract. GitAlert is in beta, so plans and limits can change; the pricing page always shows the current ones.

Which Git hosts does GitAlert support?

GitHub only today: GitAlert is a GitHub App. GitLab and Bitbucket are planned; tell us if you need one.

Is GitAlert independent of my AI agent or IDE?

Yes. GitAlert is not built by the agent that wrote the code and is not tied to any IDE or AI provider. It runs as a check on the pull request itself, so a Copilot PR, a Devin PR and a teammate's PR are all read with the same fixed rules.

Contact

Questions? Talk to us.

Tell us what you're working on and we'll help you get GitAlert running. A custom setup, a repo we don't handle well yet, a plan that doesn't fit: just ask. We're a small team, so a real person reads every message, usually the same day.

Prefer email? Write to [email protected].

Send us a message