supabase-postgres-best-practices
Pass
Audited by Gen Agent Trust Hub on Feb 20, 2026
Risk Level: SAFE
Full Analysis
- [Prompt Injection] (SAFE): No instructions found that attempt to bypass safety filters, override system prompts, or use role-play for jailbreaking. The instructional language is focused on database optimization tasks.
- [Data Exposure & Exfiltration] (SAFE): No hardcoded credentials, sensitive file paths, or network exfiltration patterns were identified. SQL examples use generic placeholders (e.g., 'user@example.com', 'xxx') and demonstrate best practices for privilege management and Row-Level Security.
- [Obfuscation] (SAFE): All content is provided in plain text markdown. No Base64 encoding, zero-width characters, or homoglyph attacks were detected.
- [Remote Code Execution] (SAFE): The repository mentions standard build tools (npm) for contributors in the README but does not include any malicious remote script execution (like curl piped to bash) or unverifiable package installations in the analyzed scope.
- [Privilege Escalation] (SAFE): While the skill discusses database privileges and roles, it does so within the context of teaching the principle of least privilege for Postgres, rather than attempting to escalate the agent's or the host system's permissions.
Audit Metadata