supabase/supabase-go

Dernière activité source enregistrée: 29 octobre 2026 à 14:08

Catalogue SkillsMP mis à jour: 2 novembre 2026 à 18:02

skills collectés: 8

Étoiles GitHub: 6
Forks GitHub: 1

Installer avec un assistant IA

Copiez ce prompt dans l’assistant IA que vous utilisez.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/supabase/supabase-go.

README du dépôt

Fichier source du README : README.md

Lire le README source

Afficher le README complet

# Supabase Go SDK The official Supabase SDK for Go. This is a multi-module monorepo, currently in early pre-release development. > [!CAUTION] > Status: Alpha. Modules are tagged for use, and their public surfaces may change in breaking ways between releases until `v1.0.0`. ## Modules | `github.com/supabase/supabase-go` module | Purpose | | ------ | ------- | | [`core`](core/) | Shared configuration, functional options and the HTTP pipeline | | [`auth`](auth/) | Auth client for server-side JWT verification and project administration | | [`postgrest`](postgrest/) | Database (PostgREST) client | | [`supabase`](supabase/) | Convenience root client composing the domains | ## Quick start Add the SDK to your module: ```bash go get github.com/supabase/supabase-go/supabase ``` Construct a client with your project URL and API key: ```go client, err := supabase.New("https://PROJECT_ID.supabase.co", "sb_publishable_...") ``` Two walkthroughs build complete Go APIs against a local Supabase stack: - The [RLS Walkthrough](docs/RLS%20Walkthrough.md) verifies each user's access token, then serves only that user's rows under Row Level Security. - The [Premium Access Walkthrough](docs/Premium%20Access%20Walkthrough.md) checks each user with Auth on every request, so a plan change or a sign-out takes effect straight away. It uses the `auth` module on its own. The package documentation on [pkg.go.dev](https://pkg.go.dev/github.com/supabase/supabase-go/supabase) covers the rest of the API. ## Supported Go versions We support the two most recent major versions of Go, aligning with the Go project's [Release Policy](https://go.dev/doc/devel/release#policy). The oldest Go version we support is referred to as our "consumer floor" and can be found in each module's `go` directive (see `go.mod` files, for example [`supabase/go.mod`](supabase/go.mod)), raised opportunistically per-module after each new Go release. ## Supabase Service Compatibility The Supabase Go SDK only guarantees compatibility with the latest release of each Supabase service, unless a minimum supported version is explicitly listed below. Older service releases are supported on a best-effort basis, but compatibility is not guaranteed. If you self-host Supabase, we recommend upgrading your services to their latest releases when upgrading the SDK. | Service | Module | Server releases | Lowest supported version | | --------- | ------------------------- | ---------------------------------------------------------------------- | ------------------------ | | Auth | [`auth`](auth/) | [supabase/auth](https://github.com/supabase/auth/releases) | Latest release | | PostgREST | [`postgrest`](postgrest/) | [PostgREST/postgrest](https://github.com/PostgREST/postgrest/releases) | Latest release | ## Security This SDK is built for backend processes that hold privileged credentials, with its security posture enforced by design: - **Zero external runtime dependencies**: the published modules require only each other, so consumers inherit no third-party code from us. - **Vulnerability scanning is continuous and scheduled**: `govulncheck` runs on every push and pull request and daily on a schedule. - **Credentials never enter logs**: silent by default, and an injected logger gets one debug record per request round trip - bodies, query strings and header values are never logged. - **Keys live only in memory**: API keys and end-user tokens are held in client configuration for the client's lifetime and never persisted. - **No Cgo**: pure Go throughout, with no memory-unsafe boundary of our own. - **Token verification is local-first**: the `auth` module verifies end-user JWTs against the project's published signing keys, deferring to the Auth server only for tokens the key set cannot verify. To report a vulnerability, see our organization-wide [security policy](https://github.com/supabase/.github/blob/main/SECURITY.md). ## Contributing and development This SDK is in pre-release and is not yet accepting external code contributions (see [`DEVELOPMENT.md`](DEVELOPMENT.md)). Also see [`standard.md`](standard.md) for our definition of "what good looks like" for a Go SDK. ## License This SDK is licensed under the MIT License - see [`LICENSE`](LICENSE).

Chargement du README du dépôt…

Skills dans ce dépôt

classification en attente

skill

métier

description

mis à jour

designing-internal-boundaries

non classé

Guides the design of internal type contracts in respect of immutability and encapsulation. Enhances codebase maintainability by separating concerns in a manner that is compiler-enforced, both for internal state as well as immutable values returned to callers…