Report policy

Anyone can scan a public GitHub repository, including one they do not own. This page explains what that means for repository owners and how to ask for a correction or removal.

What a report contains

  • The repository name, commit, scan time, and ruleset version.
  • A status, the impact on each agent, and rule findings with file paths and lines.
  • Links to the matching lines on GitHub at that commit.

A report does not store your file contents. It is an automated signal about one commit, not an accusation and not a statement about the people behind a project.

Who can see it

Reports are not listed anywhere on this site and are marked noindex for search engines. They are not private: anyone who has the link can open them.

Request a correction

For a single finding, use Report a false positive on the report. To explain a wrong result in more detail, write to [contact address to be published before launch] with the report link and what is wrong. Confirmed errors are fixed through the rules and released in a new ruleset version.

Request a removal

If you maintain the repository, write to [contact address to be published before launch] with:

  1. The report link.
  2. The repository name.
  3. How we can confirm you maintain it, such as a commit or issue from your GitHub account that mentions the request.

Removing a report deletes its findings and feedback counts, and its link and badge stop working. A cached badge can take a few minutes to disappear.

Because the repository is public, someone could scan it again, which creates a new report. The best long-term fix is to change the flagged file.

If a finding is a real problem

Treat it as you would any security report. See the rule catalog for why it was flagged and how to fix it. After you fix it, scan the new commit.