Menu

We applied the audit's fixes to the broken demo app and scanned it again. What went green, what stayed red, and what we got wrong
📰

We applied the audit's fixes to the broken demo app and scanned it again. What went green, what stayed red, and what we got wrong

DEV Community: security·Grey State Development·8 days ago
#IB6GV1xW
#devtosecurity#devto#dev#launchvet#scanner
Reading 0:00
15s threshold

Disclosure: Grey State Development built LaunchVet, the tool used here. The free core is MIT licensed. Everything below can be repeated by hand, and the demo and the fixes are in the repo.

In the first article we audited a deliberately broken resume app (ResumeFlash, Next.js, Supabase, Stripe) and listed ten of the 28 findings with their fix prompts. Reasonable question: do the prompts actually fix anything, or do they just produce a better-looking report? So we took a copy of the demo, applied the fixes, and scanned it again.

The setup, so you can judge the result. The fixes were written by Claude, following the instruction text in each finding's fix prompt, in a copy of the demo app: 32 files changed or added. Then we re-ran the LaunchVet scanner (v0.1.3) on the copy and read the code again with the judgment checks in mind. We did not build or run the app. We did not run any of the verify steps the prompts ask for (the Stripe CLI test, the two-user RLS test, the curl checks).…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.