supabase-postgres-best-practices
Pass
Audited by Gen Agent Trust Hub on Feb 17, 2026
Risk Level: LOW
Full Analysis
- [Overall Assessment] (SAFE): The skill consists entirely of instructional Markdown files. No executable scripts (.py, .js, .sh) or configuration files that trigger code execution were found.
- [Prompt Injection] (SAFE): No patterns of instruction override, role-play injection, or system prompt extraction were detected. The language is purely instructional and focused on database best practices.
- [Data Exposure & Exfiltration] (SAFE): The skill does not access sensitive local file paths or perform network operations. SQL examples use benign placeholders (e.g., 'xxx' for passwords) which are correctly identified as non-findings.
- [Unverifiable Dependencies & RCE] (SAFE): There are no package manifests (package.json, requirements.txt) and no commands that download or execute remote code (curl|bash).
- [Obfuscation] (SAFE): No Base64, zero-width characters, homoglyphs, or encoded strings were found in the documentation or metadata.
- [Indirect Prompt Injection] (SAFE): As a documentation-only skill, it does not ingest untrusted runtime data. The instructions provided are standard, industry-accepted Postgres configurations and query patterns.
- [Privilege Escalation & Persistence] (SAFE): The skill does not attempt to gain system-level privileges or establish persistence on the host machine. While it discusses database-level permissions (GRANT/REVOKE), it does so from a defensive, 'least-privilege' perspective.
Audit Metadata