supabase-extract-db-string
Database Connection String Detection
🔴 CRITICAL: PROGRESSIVE FILE UPDATES REQUIRED
You MUST write to context files AS YOU GO, not just at the end.
- Write to
.sb-pentest-context.jsonIMMEDIATELY after each discovery- Log to
.sb-pentest-audit.logBEFORE and AFTER each action- DO NOT wait until the skill completes to update files
- If the skill crashes or is interrupted, all prior findings must already be saved
This is not optional. Failure to write progressively is a critical error.
This skill detects if PostgreSQL database connection strings are accidentally exposed in client-side code.
When to Use This Skill
- As part of every security audit
- When reviewing code before production
- When Supabase database access is suspected
More from yoanbernabeu/supabase-pentest-skills
supabase-audit-rls
Test Row Level Security (RLS) policies for common bypass vulnerabilities and misconfigurations.
374supabase-pentest
Orchestrate a complete Supabase security audit with guided step-by-step execution and ownership confirmation.
240supabase-audit-auth-config
Analyze Supabase authentication configuration for security weaknesses and misconfigurations.
187supabase-audit-functions
Discover and test Supabase Edge Functions for security vulnerabilities and misconfigurations.
185supabase-help
Quick reference for all Supabase security audit skills with usage examples and command overview.
181supabase-audit-realtime
Test Supabase Realtime WebSocket channels for unauthorized subscriptions and data exposure.
174