Supabase Audit Functions
ListedHelps with Supabase, auditing as part of working with databases and data persistence workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add yoanbernabeu/supabase-pentest-skills --skill supabase-audit-functions -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
yoanbernabeu
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: abc123def.supabase.co.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
abc123def.supabase.coundeclaredWhat it found
- skills/audit-functions/supabase-audit-functions/SKILL.md:151contacts abc123def.supabase.co
curl https://abc123def.supabase.co/functions/v1/get-user-data?user_id=user-b-id \
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned yoanbernabeu/supabase-pentest-skills at 0f9612276b.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 0f9612276b
- Scanned
- 1 file, 498 lines
About this skill
The supabase-audit-functions skill enables AI agents to execute comprehensive security audits directly within Supabase projects. It automates the discovery of misconfigurations, permission leaks, and potential vulnerabilities across database schemas and Row Level Security (RLS) policies.
When to use it
- Conducting pre-deployment security checks before exposing a production database to public traffic.
- Validating that Row Level Security (RLS) policies correctly restrict data access between different user roles.
- Identifying orphaned tables or sensitive columns lacking encryption or masking configurations.
- Performing routine compliance reviews for applications handling personally identifiable information (PII).
Key capabilities
- Automated scanning of Supabase database schemas for security weaknesses.
- Analysis of Row Level Security (RLS) policy definitions and enforcement gaps.
- Detection of overly permissive authentication settings or missing access controls.
- Generation of detailed audit reports highlighting specific misconfigurations found.
Example prompts
- "Run a full security audit on my Supabase project and list any RLS policies that allow unrestricted write access."
- "Scan the database schema for tables containing sensitive data that do not have encryption enabled."
- "Identify any authentication bypass vulnerabilities or missing row-level restrictions in the current configuration."
Tips & gotchas
Ensure your AI agent has the necessary read-only credentials to safely inspect the database without modifying production data. This skill is best used as a preventative measure; always review the generated audit report manually before applying automated fixes to complex security policies.