Scan rule · RSC-ARC-013
Form without a recipient
Finds forms with input fields that have no target address in the HTML, on pages whose fully read code names no recipient either — no address to send to, no backend, no form service.
Why this matters
The typical picture in generated apps: the contact form looks finished, the submit button shows “Thanks!”, but sending was never wired up. Whoever writes to you believes they did — nothing arrives on your side, and you only notice when someone follows up.
A form without a target address is normal in a React app; the code handles submission. So we only report when **both** hold: no target in the HTML **and** nothing in the read code that accepts the input. As soon as Supabase, Firebase, an own address to send to, a server action, Netlify, Formspree, EmailJS or a site builder such as Webflow shows up, the rule stays silent.
It also stays silent when the view is incomplete: not all scripts read, subpages with their own scripts, or a script on the page that sends something itself. Verify: fill in the form, submit it and watch the “Network” tab in the browser's developer tools — if no request goes out, the message goes nowhere.
Scan tier
How to fix it
Wire up the submission: to your own server endpoint, to the database or to a form service — and send yourself a test message once.