supabase-rate-limits

No clear malicious behavior or embedded malware is present. The principal risks are plaintext database passwords in Example 2, use of a privileged service-role key in Example 1, unauthenticated and unvalidated webhook ingestion, and direct exposure of database error messages. The examples should use placeholders, secret-management guidance, webhook authentication, strict schema and size validation, and generic client-facing errors.