{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/568f5bb5a2d04286b8c8a803de925843\" frameborder=\"0\" width=\"3024\" height=\"2268\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":2268,"width":3024,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":2268,"thumbnail_width":3024,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/568f5bb5a2d04286b8c8a803de925843-c8781de5f79f5190.gif","duration":372.247,"title":"PR Dev Sentinel for GitHub Secret Scanning","description":"This Loom introduces PR Dev Sentinel, a Meta AI Hackathon project that prevents secret leaks from getting merged via pull request diffs and commit history. The author explains how many secret scanners miss cases where developers delete keys in the PR while the secrets remain in Git history, commit messages, or removed lines, and how their tool acts as a merge gate. They demonstrate a workflow with a website, a Chrome extension, and a CLI webhook, including a test case where the scan fails due to eight blocking findings with six still live in the repository, such as a GitHub personal authentication token and leaked DB URL and AWS keys. The report provides masked hits labeling and rotate steps, plus suggested patches and a chat-like interface to ask for fixes."}