# supabase-community/supabase-csharp

> supabase-csharp is the official C# client library for Supabase, used from .NET code to reach Supabase services. It provides a unified Supabase client that wires together separate service packages for authentication, database queries, file storage, realtime messaging and Edge Functions, and each service package can also be referenced on its own. The library is written in C#.

Source: https://github.com/supabase-community/supabase-csharp
Indexed: commit 0d58f45 on 2026-08-17 by Repowise. Facts come from the source and git history, not from the maintainer.

## Facts

- Language: C#
- Stars: 710 at index time
- License: MIT
- Code health: 9.0/10, Excellent
- Last commit: 2026-08-14
- Contributors: 14

## Install

From the README: https://github.com/supabase-community/supabase-csharp#installation

Clone the supabase-csharp repository.
    git clone https://github.com/supabase-community/supabase-csharp.git

Move into the supabase-csharp folder.
    cd supabase-csharp

Install the Supabase package from NuGet into a .NET project.
    dotnet add package Supabase

Restore the NuGet dependencies when building the repository from source.
    dotnet restore

Build the solution in Release configuration.
    dotnet build Supabase.sln --configuration Release

## How it works

Application code starts from the unified client in packages/Supabase, which exposes the services as properties such as Auth, Storage, Realtime and Functions, plus a From method for database queries. Each service lives in its own package under packages/, including packages/Gotrue for authentication and packages/Postgrest for queries through the auto-generated REST API. Shared primitives used by those service packages sit in packages/Core, which is rarely referenced directly. Each package directory holds a library project and a test project, and metadata common to all projects is set in Directory.Build.props. Dependency versions are managed centrally in Directory.Packages.props, and the .NET SDK version is pinned in global.json. The clients emit traces and metrics through System.Diagnostics, so OpenTelemetry can subscribe to them without a direct dependency on its packages.

- .claude/skills/sdk-quality-gate/SKILL.md: central file
- .documentation/docfx.json: central file
- .documentation/index.md: central file
- .documentation/toc.yml: central file
- .gate-config.json: central file
Modules: packages, supabase, root, scripts, .documentation, .github, docs, .claude. 455 files, 26,908 lines, 4,220 symbols.

## Code health

- Score: 9.0/10 (Excellent)
- Rank: #17 of 4,000+ indexed repos
- Hotspots: packages/Gotrue/Gotrue.Tests/Support/MockGotrueServer.cs
- Lowest file: packages/Postgrest/Postgrest/Table.cs
- Dead code: 70 findings

## Maintenance

- Last commit 2026-08-14, first commit 2020-08-07, 339 commits
- 14 contributors, bus factor 1

## Security

- Security findings are shown to signed-in users at https://repowise.dev/repo/supabase-community/supabase-csharp/security

## More

- Page: https://repowise.dev/repo/supabase-community/supabase-csharp
- Ask this codebase: https://repowise.dev/repo/supabase-community/supabase-csharp/chat
- Docs: https://repowise.dev/repo/supabase-community/supabase-csharp/docs
- MCP (signs in with Repowise on first use):
    claude mcp add --transport http repowise https://api.repowise.dev/mcp/supabase-community/supabase-csharp
