All demosCommit Sentry
Commit Sentry
Review a staged code change for exposed secrets, risky edits and a misleading commit message.
Powered by/yes-no/classify/rate
Performance & cost
This page session · since page load
- Typical request time
- —
- Input tokens
- 0
- Estimated cost · USD
- $0.00
How these numbers work · 0 successful requests
- Model compute
- —
- Successful requests
- 0
Average per measured successful request.
Run the demo to measure live requests.
Request time is the median time for a successful request, including queue, network, and retries. One request can judge many inputs: model compute adds their processing time and can exceed browser time.
Input tokens come from API response headers. Cost is estimated at $0.04 per million input tokens, before plan credits. Missing usage is marked unavailable or as a partial total (≥). Demo resets keep these totals; reload the page to start a new session.
Select Run check, then open a file or finding to see the affected lines.
How it works
The demo checks a sample diff in batches, combining line-level signals, change categories and risk ratings. A policy turns those signals into findings and a pass, warning or block decision.
Demo scope
The diff is a sample, and no repository is changed. Destructive SQL signals are advisory because they do not reliably distinguish safe queries. A passing result is not a complete security review.
Inspired by the work of dabit3.