Code & supply chain
Secret leak detection
Full repository history scanned daily for accidentally-committed secrets.
Healthy
0 leaked secrets in history
Checked 9/20/2026, 2:20:44 AM · Source: Continuous integration
Full repository history scanned for accidentally-committed credentials. Pre-commit hooks block this at the developer's machine; this is the belt-and-braces check.
What this check means
Even if a secret is rotated, a leaked secret in version-control history is recoverable forever. A daily scan asserts that no API keys, tokens, or other credentials have ever been committed. Nothing blocks a secret at commit time today — this scan is detection, not prevention, which is why the window between commit and detection is at most 24 hours.
Recent runs
| When | Result | Source | |
|---|---|---|---|
| 9/20/2026, 2:20:44 AM | 0 leaked secrets in history | Continuous integration | |
| 9/19/2026, 2:20:03 AM | 0 leaked secrets in history | Continuous integration | |
| 9/18/2026, 2:20:10 AM | 0 leaked secrets in history | Continuous integration | |
| 9/17/2026, 2:20:56 AM | 0 leaked secrets in history | Continuous integration | |
| 9/16/2026, 2:20:48 AM | 0 leaked secrets in history | Continuous integration | |
| 9/15/2026, 2:21:29 AM | 0 leaked secrets in history | Continuous integration | |
| 9/14/2026, 2:23:57 AM | 0 leaked secrets in history | Continuous integration | |
| 9/13/2026, 2:20:40 AM | 7 potential secrets found | Continuous integration | |
| 9/12/2026, 2:20:22 AM | 3 potential secrets found | Continuous integration | |
| 9/11/2026, 2:21:09 AM | 0 leaked secrets in history | Continuous integration | |
| 9/10/2026, 2:21:13 AM | 0 leaked secrets in history | Continuous integration | |
| 9/9/2026, 2:20:35 AM | 0 leaked secrets in history | Continuous integration | |
| 9/8/2026, 2:20:27 AM | 0 leaked secrets in history | Continuous integration | |
| 9/7/2026, 2:22:09 AM | 0 leaked secrets in history | Continuous integration | |
| 9/6/2026, 2:20:43 AM | 0 leaked secrets in history | Continuous integration | |
| 9/5/2026, 2:19:56 AM | 0 leaked secrets in history | Continuous integration | |
| 9/4/2026, 2:21:00 AM | 0 leaked secrets in history | Continuous integration | |
| 9/3/2026, 2:37:41 AM | 0 leaked secrets in history | Continuous integration | |
| 9/2/2026, 2:37:19 AM | 0 leaked secrets in history | Continuous integration | |
| 9/1/2026, 2:22:30 AM | 0 leaked secrets in history | Continuous integration | |
| 8/31/2026, 2:22:13 AM | 0 leaked secrets in history | Continuous integration | |
| 8/30/2026, 2:20:47 AM | 0 leaked secrets in history | Continuous integration | |
| 8/29/2026, 2:18:15 AM | 0 leaked secrets in history | Continuous integration | |
| 8/28/2026, 4:49:28 AM | 0 leaked secrets in history | Continuous integration | |
| 8/27/2026, 3:51:21 AM | 0 leaked secrets in history | Continuous integration | |
| 8/26/2026, 2:34:17 AM | 0 leaked secrets in history | Continuous integration | |
| 8/25/2026, 2:29:20 AM | 0 leaked secrets in history | Continuous integration | |
| 8/24/2026, 2:32:55 AM | 0 leaked secrets in history | Continuous integration | |
| 8/23/2026, 2:32:58 AM | 0 leaked secrets in history | Continuous integration | |
| 8/22/2026, 2:26:57 AM | 0 leaked secrets in history | Continuous integration |
Need additional detail (sanitised report, supporting evidence)? security@theartofcto.com