Security
Security checks in every review.
Every SourceAnt review scans your pull request for security issues with Semgrep before the AI reads the change.
Free for 250 events a month. Unlimited seats. Your own model keys.
Problem
A model should not spend a pass on what a tool already knows.
Static analysis finds known patterns quickly and the same way every time. SourceAnt runs it first, so the review spends its attention elsewhere.
Today: Semgrep
Semgrep-based static analysis runs inside every code review. Nothing extra to install.
Planned: open scanners
OWASP ZAP, Nuclei, Trivy and Gitleaks are planned. None of them runs today.
How
From the first signal to the next action.
01
Analyse
Semgrep checks the changed files with its default rules. It reads more than thirty languages without installing their toolchains.
02
Ground
Its findings reach the review as fact. A model comment on the same lines is dropped as already covered.
03
Scan
Planned: open pentesting and scanning tools such as OWASP ZAP, Nuclei, Trivy and Gitleaks.
Docs
Fewer repeated findings.
What a tool already found is not repeated by the model, so the comments you read are the ones a tool could not write.
Read the security documentationFAQ
Before you get started.
Which scanners run today?
Semgrep, inside every code review. OWASP ZAP, Nuclei, Trivy and Gitleaks are planned and not available yet.
Does the model repeat what Semgrep found?
No. A model comment on lines Semgrep already flagged is dropped as already covered.