Metal Mantra / AGENT INTELLIGENCEFINDING DISCLOSURE · 12 OCT 2026AUTOMATED SIGNAL. NOT CERTIFICATION.
05 / 05FINDING DISCLOSURE · 12 OCT 2026

Public code, public findings.

Reports of public GitHub repositories show every finding in full, critical ones included, from the moment they are published.

01

Why findings are not hidden

The code is already public; anyone can read it. People deciding whether to run or buy an agent need to know what the scan found now, not after a delay, so they can protect themselves. Each finding shows its rule, explanation, suggested fix and a link to the exact file and line at the scanned commit.

02

What is never shown

Secret values are never printed. A hardcoded-credential finding names the file and line, not the key. Reports built from private evidence (a CI-attested scan of a private repository, or an endpoint-only check) still withhold critical details from public view for 30 days, because nobody else can see that source.

03

What this is not

Findings are automated static heuristics, not confirmed vulnerabilities and not a security certification. Metal Mantra does not run a coordinated disclosure service and does not guarantee to notify maintainers before a report is published. A person who initiated a scan is not necessarily the repository maintainer.

04

Maintainers: fix, re-scan or ask for review

Fix the code and run a new scan; the newest public report replaces the old one. If a finding is wrong or especially sensitive, send the report URL and context through the support form or email security@metalmantra.io. If you find a live credential in your repository, rotate it first. Do not put exploit details or secrets in a public URL.