supabase-developer

No clear indicators of intentional malware/backdoors (no suspicious network callbacks, persistence, or dynamic execution) in this module. However, the code has high security risk due to (1) credential leakage risk by logging all request headers (often including Authorization bearer tokens) and (2) inconsistent and potentially missing authorization scoping in PUT and DELETE (and partially in GET/DELETE), which can lead to cross-user data modification/deletion if Supabase RLS/policies are not perfectly restrictive. This should be treated as a security-critical logic issue rather than a safe dependency.