supabase-audit-functions
Edge Functions Audit
🔴 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 function tested- Log to
.sb-pentest-audit.logBEFORE and AFTER each function test- 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 discovers and tests Supabase Edge Functions for security issues.
When to Use This Skill
- To discover exposed Edge Functions
- To test function authentication requirements
- To check for input validation issues
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-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.
174supabase-audit-rpc
List and test exposed PostgreSQL RPC functions for security issues and potential RLS bypass.
169