Loading the registry…
Access your Supabase projects and perform tasks like managing tables, fetching config, and querying data.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
4 critical findings reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
This artifact ships from 2 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/supabase-community/supabase-plugin, 51 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- supabase
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
16 findings · 7.4s
v0.3.74
35 findings · 0.8s
v0.1.0
0 findings · 2.7s
v0.1.0
0 findings · 6.8s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 2.7s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
2 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 3, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: complete | rejected |
| Aug 12, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 51 findings across every scanner that examined this package. None of the 4 findings rated critical by their scanner were dismissed.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
22 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: AAK-AGENT-002 · Files: AGENTS.md, CLAUDE.md · reported by agent-audit-kit
2 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/release.yml, .github/workflows/sync-agent-skills.yml · reported by agent-audit-kit
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
7 HIDDEN_DATA_FILE
Files: /repo/.plugin/plugin.json, /repo/.cursor-plugin/plugin.json, /repo/.release-please-manifest.json and 4 more · reported by cisco-skill-scanner
5 MANIFEST_MISSING_LICENSE
Files: /repo/skills/supabase/SKILL.md, /repo/SKILL.md, /repo/skills/supabase-postgres-best-practices/references/SKILL.md and 2 more · reported by cisco-skill-scanner
4 AAK-MCP-001
Files: agents/open-plugin/.mcp.json, agents/copilot/.mcp.json, agents/claude/.mcp.json and 1 more · reported by agent-audit-kit
4 AAK-MCP-ATTEST-001
Files: agents/open-plugin/.mcp.json, agents/copilot/.mcp.json, agents/claude/.mcp.json and 1 more · reported by agent-audit-kit
4 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/skills/supabase-postgres-best-practices/references/SKILL.md, /repo/skills/supabase/references/SKILL.md and 1 more · reported by cisco-skill-scanner
Critical policy files are missing or incomplete.
The artifact contains critical findings related to missing or incomplete policy files in agent configurations, specifically within `agents/claude/.mcp.json`, `agents/copilot/.mcp.json`, `agents/grok/mcp.json`, and `agents/open-plugin/.mcp.json`. Additionally, high-severity findings indicate the presence of sensitive information or credentials within documentation files such as `SUPABASE.md` and `skills/supabase-postgres-best-practices/references/security-privileges.md`. These issues warrant attention due to potential implications for system integrity and data exposure.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
3 AAK-IPI-WILD-CORPUS-001
Files: SUPABASE.md, skills/supabase-postgres-best-practices/references/security-privileges.md, skills/supabase-postgres-best-practices/references/schema-partitioning.md · reported by agent-audit-kit