Yesterday @andriosr shared Fence, the first side project from the hoop.dev team. Today we're launching the second one: Risk Summary.
This one was born when we were at our offsite. We were talking about problems our customers see that shouldn't live inside hoop.dev but are adjacent to our product and this one was relevant: what's actually in your AI coding session logs? Every paste, config, and stack trace your agent read is sitting in a file on your disk. Our thinking is that nobody wants to open it, but they should have the ability to know.
hoopRS runs one command, and you get your report: Entity types, counts, and severities. But never the values. So you can share the scan without leaking anything.
Currently hoopRS reads Claude Code, Cursor and OpenCode sessions.
And it's free. No signup walls, no trials.
Yesterday @andriosr shared Fence, the first side project from the hoop.dev team. Today we're launching the second one: Risk Summary.
This one was born when we were at our offsite. We were talking about problems our customers see that shouldn't live inside hoop.dev but are adjacent to our product and this one was relevant: what's actually in your AI coding session logs? Every paste, config, and stack trace your agent read is sitting in a file on your disk. Our thinking is that nobody wants to open it, but they should have the ability to know.
hoopRS runs one command, and you get your report: Entity types, counts, and severities. But never the values. So you can share the scan without leaking anything.
Currently hoopRS reads Claude Code, Cursor and OpenCode sessions. And it's free. No signup walls, no trials.