I m a solo dev working on API Radar a live feed of leaked API keys and secrets found in public GitHub repos. Later today I m shipping a big rebuild of the search/detection engine, and I d love to sanity check a few things with this crowd before it goes fully live on Product Hunt.
A couple of questions for folks in security, DevOps/SRE, or backend roles:
What s the most useful way to present this kind of data so it actually helps you fix issues? (per repo view, per provider, timelines, alerts, something else?)
Where s the ethical line for you? The data is from public repos only, but what would make a tool like this clearly defensive and helpful rather than sketchy or abusable?
Blunt feedback is welcome on the idea, UX, or even whether this should exist at all.
API Radar – Live Feed of Leaked API Keys
That def would be helpful. It would also help to see if keys have already been rotated, most of the times if keys are leaked they're rotated since it's already in git history
API Radar – Live Feed of Leaked API Keys
@bekjon_ibragimov 100% agree.
right now api radar shows leaks with the latest ones first, so if a owner pushed a key 10 hours ago, the chances are high that the key is still active
Dirac
What if an attacker uses Api radar before you do? :p
API Radar – Live Feed of Leaked API Keys
@peterz_shu Legit concern.
API Radar does scan public GitHub, so that risk is always on my mind.