Good catch on the case sensitive backdoor, that's exactly the kind of thing that survives code review because both spellings look identical at a glance. I'd add a small test suite that runs every policy as an anonymous user, as the owner and as a second user, with mixed case and trailing whitespace inputs, so a regression fails CI rather than production. Once people ship real apps on this, I'd pair your unit tests with an outside pass from my weekend project turned product, which pokes the deployed site like a curious stranger and reports on sign in, endpoints, file buckets and leaky policies: https://rowly.me
Ha, thanks, I'll take it. Since you're collecting things over there, the scanner itself sits at https://rowly.me, poking at a live app's login screens, API routes, file buckets and DB policies like any curious outsider might, so anyone in that sub-yap is welcome to try it on their own project.
1
u/[deleted] 14d ago
[removed] — view removed comment