supabase-server
Build Secure Supabase Server Endpoints
Server-side Supabase authentication and client setup can be easy to misconfigure. This skill provides current patterns for secure handlers, webhooks, adapters, and migrations.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "supabase-server" from https://skillstore.io/skills/supabase-supabase-server.md and its manifest at https://skillstore.io/api/skills/supabase-supabase-server/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « supabase-server ». Create a user-authenticated function that returns the current user todo list.
Résultat attendu:
A Deno Edge Function design using user authentication, a context-scoped client, structured errors, and the required npm import format.
Utilisation de « supabase-server ». Accept Stripe checkout webhooks and mark matching orders as paid.
Résultat attendu:
- A public handler that verifies the Stripe signature before processing events.
- Secret configuration guidance for Stripe credentials and webhook verification.
- A scoped database update using the administrative Supabase client.
Utilisation de « supabase-server ». Update an older function that uses service-role and anonymous keys.
Résultat attendu:
A migration plan mapping legacy key usage to explicit authentication modes while preserving caller verification and administrative database access.
Audit de sécurité
SûrAll 120 static alerts are false positives caused by Markdown formatting, documentation links, placeholder credentials, or legitimate server examples. SKILL.md contains no executable audit-time scripts, dynamic code construction, shell substitution, secret exfiltration, or prompt injection. Documented network and environment access is scoped to user-authored Supabase and Stripe integrations.
Facteurs de risque
⥠Contient des scripts (1)
âïž Commandes externes (50)
đ AccĂšs rĂ©seau (7)
đ Variables dâenvironnement (5)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/supabase-supabase-server/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/supabase-supabase-server?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/supabase-supabase-server?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/supabase-supabase-server/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/supabase-supabase-server.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citations académiques (APA · BibTeX · CFF)
Citation APA
supabase. (2026). supabase-server security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/supabase-supabase-server/audits/1Citation BibTeX
@techreport{supabase-supabase-supabase-server-2026,
author = {supabase},
title = {supabase-server security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/supabase-supabase-server/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "supabase-server security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "supabase"
date-released: "2026-08-21"
url: "https://skillstore.io/skills/supabase-supabase-server/audits/1"
identifiers:
- type: other
value: "skillstore:supabase-supabase-server:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Create Edge Functions
Build authenticated Supabase Edge Functions with the correct runtime imports, clients, and platform configuration.
Add Framework Authentication
Integrate per-route Supabase authentication into Hono, Cloudflare Workers, or cookie-based server frameworks.
Modernize Existing Functions
Replace legacy keys, CDN imports, manual clients, and deprecated authentication options with current server patterns.
Essayez ces prompts
Create a Supabase Edge Function that lists todos for an authenticated user. Use @supabase/server, user authentication, and clear error handling.
Add @supabase/server authentication to this Hono application. Protect [route] for signed-in users and preserve the existing response behavior.
Design a Supabase Edge Function for [provider] webhooks. Verify the provider signature before database updates and explain required secret configuration.
Migrate this legacy Supabase server code to @supabase/server: [code]. Preserve authorization intent, update keys and imports, and identify configuration changes.
Bonnes pratiques
- Confirm endpoint access requirements before choosing an authentication mode.
- Keep secrets in platform secret storage and use named keys for isolated services.
- Verify external webhook signatures before parsing events or changing database records.
Ăviter
- Do not use unauthenticated mode for sensitive reads, writes, or administrative actions.
- Do not embed real API keys in source files, prompts, logs, or example requests.
- Do not copy legacy auth names or environment keys into new implementations.