CybersecurityInvestigation

Incident Response

Confirm whether a leaked key traces back to a public repo during an incident.

Start with 500 free credits Documentation

GitHub leaks · 1 credit per leak per lookup · no monthly fee

How it works

One call, structured answer

Incident Response runs on the github leaks lookup at 1 credit per leak per lookup. Same API key, same JSON shape as every other Encrata lookup.

Scans the full git history, not just the current HEAD
Finds API keys, tokens and private keys with file and line context
A clean repository costs nothing, you only pay per leak found
Findings export cleanly into your ticketing and remediation flow

Terminal

curl -X POST "https://developer.encrata.com/api/breaches/github" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"repo": "https://github.com/acme/checkout"}'

response.json

{
  "repo": "acme/checkout",
  "findings": [
    { "rule": "aws-access-key", "severity": "critical", "path": "config/prod.env", "line": 12 }
  ],
  "credits": 1
}