cync-cli 0.3.0__tar.gz

cync_cli-0.3.0/.dockerignore

@@ -0,0 +1,16 @@
+client/
+scripts/
+supabase/
+.venv/
+.git/
+.github/
+__pycache__/
+**/__pycache__/
+*.pyc
+*.egg-info/
+.env
+.env.*
+node_modules/
+.svelte-kit/
+.vercel/
+.DS_Store

cync_cli-0.3.0/.env.example

@@ -0,0 +1,36 @@
+# ---- cync server (.env) ----
+
+# Blob storage backend: "r2" (default) or "local" (filesystem, for testing)
+CYNC_STORAGE=r2
+# CYNC_LOCAL_DIR=~/.cync-store   # only used when CYNC_STORAGE=local
+
+# Cloudflare R2 (transcript blobs) — R2 dashboard -> Manage R2 API Tokens
+# Create a token with Object Read & Write.
+R2_ACCOUNT_ID=your_cloudflare_account_id
+R2_ACCESS_KEY_ID=your_r2_access_key_id
+R2_SECRET_ACCESS_KEY=your_r2_secret_access_key
+R2_BUCKET=cync
+# Optional: set R2_ENDPOINT directly instead of R2_ACCOUNT_ID
+# R2_ENDPOINT=https://<account_id>.r2.cloudflarestorage.com
+
+# Supabase (GitHub auth + Postgres metadata) — Project Settings -> API
+SUPABASE_URL=https://<ref>.supabase.co
+SUPABASE_ANON_KEY=your_supabase_anon_key
+SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key
+
+# Where the server listens
+CYNC_HOST=127.0.0.1
+CYNC_PORT=8787
+# CYNC_MAX_BODY_BYTES=67108864   # 64 MB request-body cap
+
+# ---- hosted-service policy (optional) ----
+# Access: restrict to specific GitHub emails/usernames (comma-separated). Empty = open.
+# CYNC_ALLOWLIST=you@example.com,yourgithubusername
+# Per-user quotas (public/open mode):
+# CYNC_MAX_PROJECTS=20
+# CYNC_MAX_BYTES_PER_USER=524288000   # 500 MB per user
+
+# ---- CLI (each machine) ----
+# Point the CLI at your server (env var, or ~/.config/cync/config.toml `server_url`).
+# Must be https:// except on localhost.
+# CYNC_SERVER_URL=http://127.0.0.1:8787

cync_cli-0.3.0/.github/workflows/publish.yml

@@ -0,0 +1,28 @@
+name: publish
+
+# Publish the CLI to PyPI when a version tag (v*) is pushed.
+# Uses PyPI Trusted Publishing (OIDC) — no API token stored in the repo.
+# One-time PyPI setup: pypi.org -> project cync-cli -> Publishing -> add a
+# GitHub trusted publisher (owner: 03hgryan, repo: cync, workflow: publish.yml).
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read # actions/checkout needs repo read access
+      id-token: write # required for PyPI trusted publishing (OIDC)
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Build sdist + wheel
+        run: |
+          python -m pip install --upgrade build
+          python -m build
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

cync_cli-0.3.0/.gitignore

@@ -0,0 +1,11 @@
+.venv/
+__pycache__/
+*.pyc
+*.egg-info/
+dist/
+build/
+.env
+.DS_Store
+node_modules/
+.svelte-kit/
+web/build/

cync_cli-0.3.0/Dockerfile

@@ -0,0 +1,13 @@
+# cync API server (FastAPI) — container for Cloud Run / any Docker host.
+FROM python:3.12-slim
+
+WORKDIR /app
+
+# Install the package + server extras (fastapi, uvicorn, boto3, pydantic).
+COPY pyproject.toml ./
+COPY src ./src
+RUN pip install --no-cache-dir ".[server]"
+
+ENV CYNC_STORAGE=r2
+# Cloud Run injects $PORT (defaults to 8080); bind all interfaces.
+CMD ["sh", "-c", "uvicorn cync.server:app --host 0.0.0.0 --port ${PORT:-8080}"]

cync_cli-0.3.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 03hgryan
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

cync_cli-0.3.0/PKG-INFO

@@ -0,0 +1,176 @@
+Metadata-Version: 2.4
+Name: cync-cli
+Version: 0.3.0
+Summary: Sync Claude Code conversations across machines — GitHub-authed CLI + server (Postgres metadata, R2 blobs).
+Project-URL: Homepage, https://github.com/03hgryan/cync
+Project-URL: Repository, https://github.com/03hgryan/cync
+Author: 03hgryan
+License: MIT License
+        
+        Copyright (c) 2026 03hgryan
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+License-File: LICENSE
+Keywords: claude,claude-code,cli,conversations,sync
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Utilities
+Requires-Python: >=3.11
+Requires-Dist: httpx<1,>=0.27
+Requires-Dist: python-dotenv<2,>=1.0
+Requires-Dist: rich<15,>=13
+Requires-Dist: typer<1,>=0.12
+Provides-Extra: dev
+Requires-Dist: boto3<2,>=1.34; extra == 'dev'
+Requires-Dist: fastapi<1,>=0.110; extra == 'dev'
+Requires-Dist: pydantic<3,>=2; extra == 'dev'
+Requires-Dist: pytest<9,>=8; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Requires-Dist: uvicorn[standard]<1,>=0.29; extra == 'dev'
+Provides-Extra: server
+Requires-Dist: boto3<2,>=1.34; extra == 'server'
+Requires-Dist: fastapi<1,>=0.110; extra == 'server'
+Requires-Dist: pydantic<3,>=2; extra == 'server'
+Requires-Dist: uvicorn[standard]<1,>=0.29; extra == 'server'
+Description-Content-Type: text/markdown
+
+# cync — code sync for Claude Code conversations
+
+Sync your Claude Code conversations across machines, signed in with **GitHub**.
+Your conversation **metadata** lives in your **Supabase** Postgres (per-user, RLS),
+the **transcripts** live in your **Cloudflare R2** bucket, and a small FastAPI
+server brokers both. Like git, but for your chats: `cync push` on one machine,
+`cync pull` on another, and `claude --resume` picks up where you left off — plus
+a web viewer to browse them.
+
+```
+Browser / CLI ── GitHub login (Supabase Auth) ──┐
+                                                 ▼ JWT
+                                            FastAPI  ── Postgres (metadata, per-user RLS)
+                                                     ── R2 (transcript blobs)
+```
+
+## How it works
+- Sign in once per machine with `cync login` (GitHub via Supabase, browser PKCE).
+- A **project** is a first-class record you own; create one with `cync init <name>`
+  and link a directory to it. Conversations are keyed by their Claude session UUID.
+- `push` uploads `~/.claude/projects/<repo>/<id>.jsonl`; `pull` writes it back on the
+  other machine and rewrites the embedded `cwd` so `claude --resume` just works.
+- Everything is scoped to your GitHub user — projects/conversations are private to you.
+
+## Install & use (hosted)
+
+The CLI is on PyPI as **`cync-cli`** (the command is `cync`). No server setup —
+it points at the hosted cync by default:
+
+```bash
+pipx install cync-cli        # or: uv tool install cync-cli
+cync login                   # sign in with GitHub
+cd ~/path/to/your/project
+cync init myproject && cync push     # machine A
+cync link myproject && cync pull     # machine B → claude --resume
+```
+
+## Self-hosting
+
+Prefer your own stack? Point the CLI at your deployment via `CYNC_SERVER_URL`
+(env or `~/.config/cync/config.toml`), then deploy the server + provision your
+own Supabase + R2:
+
+### 1. Provision (one time)
+- **Cloudflare R2:** create a bucket (default name `cync`) and an API token with
+  **Object Read & Write**.
+- **Supabase:** create a project, then run [`supabase/schema.sql`](supabase/schema.sql)
+  in the SQL editor. Enable **Auth → Providers → GitHub** (create a GitHub OAuth App
+  with callback `https://<ref>.supabase.co/auth/v1/callback`). Under **Auth → URL
+  Configuration**, add redirect URLs `http://127.0.0.1:8765/callback` (CLI) and
+  `http://localhost:5173/auth/callback` (web).
+
+### 2. Server
+```bash
+uv venv && source .venv/bin/activate
+uv pip install -e ".[server]"
+cp .env.example .env     # fill in R2_* and SUPABASE_* (URL, anon, service_role)
+cync-server              # http://127.0.0.1:8787
+```
+> For cross-machine use, expose the server over **HTTPS** (Tailscale, Fly.io, Railway).
+> The CLI refuses non-HTTPS server URLs except on localhost.
+
+### 3. CLI (each machine)
+```bash
+uv pip install -e .                      # base install
+export CYNC_SERVER_URL=http://127.0.0.1:8787   # or your https URL / config.toml
+cync login                               # sign in with GitHub (opens a browser)
+
+cd ~/path/to/your/project
+cync init droneforge                     # create + link a project (machine A)
+cync push
+# on machine B:  cync link droneforge && cync pull  →  claude --resume
+```
+
+### 4. Web viewer (optional)
+```bash
+cd client
+pnpm install
+cp .env.example .env   # PUBLIC_SUPABASE_URL, PUBLIC_SUPABASE_ANON_KEY, CYNC_SERVER_URL
+pnpm dev               # http://localhost:5173 → "Sign in with GitHub"
+```
+The SvelteKit server holds the token (Supabase SSR cookies); browse at `/p/<project>`.
+
+## Commands
+| Command | What it does |
+|---|---|
+| `cync login` / `logout` / `whoami` | GitHub auth session |
+| `cync init <name>` | create a project + link this directory |
+| `cync link <name>` | link this directory to an existing project |
+| `cync unlink` | remove this directory's link |
+| `cync push [id]` | upload this project's conversation(s) |
+| `cync pull [id]` | download into `~/.claude` (overwrite/add) |
+| `cync list` | list this project's conversations |
+| `cync project list` / `rm <name>` | manage your projects |
+
+## Migrating from v0.2
+If you have v0.2 (static-token) data still in R2, after `cync login`:
+```bash
+python scripts/migrate_legacy.py --slug <name> --email <your-github-email> [--purge]
+```
+Or simply re-`cync push` from a machine that has the conversations locally.
+
+## Security
+- Per-user GitHub auth (Supabase JWT); every project/conversation is owner-scoped,
+  with Postgres RLS as a backstop. The server holds R2 + Supabase keys; clients never do.
+- CLI login uses PKCE + a single-use loopback callback; the session (refresh token)
+  is stored `0600` at `~/.config/cync/session.json`.
+- Request bodies are capped (`CYNC_MAX_BODY_BYTES`, default 64 MB).
+
+## Layout
+```
+src/cync/        server (FastAPI), CLI, auth, Supabase + R2 stores
+client/          SvelteKit web viewer (GitHub login)
+supabase/        Postgres schema + RLS
+scripts/         legacy migration
+```
+
+## Limitations
+- Last-writer-wins; no version history yet.
+- Syncs the `.jsonl` transcript only (enough for `--resume`); not `todos/` sidecars.
+- Don't `push` a conversation that's open in Claude Code — quit first so it isn't mid-write.
+- Listing reads one object per conversation from Postgres (fine for personal scale).

cync_cli-0.3.0/PRIVACY.md

@@ -0,0 +1,61 @@
+# cync — Privacy Policy
+
+_Last updated: 2026-07-02. This is a starting template — review and adapt it (and
+consult a professional) before relying on it for a public service._
+
+cync ("the service") syncs your Claude Code conversations across machines. This
+explains what it stores and how the data is handled.
+
+## What we collect
+
+- **Identity:** when you sign in with GitHub (via Supabase Auth), we store your
+  GitHub account id, email, and username.
+- **Conversations you push:** the Claude Code conversation transcripts you choose
+  to `cync push` — stored as files in Cloudflare R2, with metadata (title, size,
+  timestamps, project) in Supabase Postgres.
+
+We do **not** access your GitHub repositories or anything beyond your basic
+profile and the conversations you explicitly push.
+
+## ⚠️ Conversation content
+
+Transcripts can contain whatever you and Claude typed — source code, file paths,
+and potentially **secrets or personal data**. Only push conversations you're
+comfortable storing. You are responsible for the content you upload.
+
+## Who can see your data
+
+- Your projects and conversations are **isolated per user** by database
+  row-level security — other users cannot access them.
+- The service operator has **technical access** to the underlying storage (via
+  administrative keys) as needed to operate, maintain, and debug the service. The
+  operator does not view your conversation content except as necessary to run the
+  service or to comply with the law.
+
+## Where it's stored
+
+- **Cloudflare R2** (conversation files) and **Supabase Postgres** (metadata +
+  auth), both encrypted at rest by those providers. Hosting: **Google Cloud Run**.
+
+## Retention & deletion
+
+- Delete a project and all its conversations any time with `cync project rm <name>`.
+- To delete your account and all associated data, contact **gimogunn@gmail.com**.
+
+## Third parties
+
+We rely on GitHub (authentication), Supabase (auth + metadata), Cloudflare R2
+(storage), and Google Cloud (hosting). We do **not** sell your data, and there is
+no advertising.
+
+## Cookies
+
+The web viewer sets a Supabase authentication cookie solely to keep you signed in.
+
+## Changes
+
+We may update this policy; material changes are reflected by the date above.
+
+## Contact
+
+Questions or deletion requests: **gimogunn@gmail.com**.

cync_cli-0.3.0/README.md

@@ -0,0 +1,122 @@
+# cync — code sync for Claude Code conversations
+
+Sync your Claude Code conversations across machines, signed in with **GitHub**.
+Your conversation **metadata** lives in your **Supabase** Postgres (per-user, RLS),
+the **transcripts** live in your **Cloudflare R2** bucket, and a small FastAPI
+server brokers both. Like git, but for your chats: `cync push` on one machine,
+`cync pull` on another, and `claude --resume` picks up where you left off — plus
+a web viewer to browse them.
+
+```
+Browser / CLI ── GitHub login (Supabase Auth) ──┐
+                                                 ▼ JWT
+                                            FastAPI  ── Postgres (metadata, per-user RLS)
+                                                     ── R2 (transcript blobs)
+```
+
+## How it works
+- Sign in once per machine with `cync login` (GitHub via Supabase, browser PKCE).
+- A **project** is a first-class record you own; create one with `cync init <name>`
+  and link a directory to it. Conversations are keyed by their Claude session UUID.
+- `push` uploads `~/.claude/projects/<repo>/<id>.jsonl`; `pull` writes it back on the
+  other machine and rewrites the embedded `cwd` so `claude --resume` just works.
+- Everything is scoped to your GitHub user — projects/conversations are private to you.
+
+## Install & use (hosted)
+
+The CLI is on PyPI as **`cync-cli`** (the command is `cync`). No server setup —
+it points at the hosted cync by default:
+
+```bash
+pipx install cync-cli        # or: uv tool install cync-cli
+cync login                   # sign in with GitHub
+cd ~/path/to/your/project
+cync init myproject && cync push     # machine A
+cync link myproject && cync pull     # machine B → claude --resume
+```
+
+## Self-hosting
+
+Prefer your own stack? Point the CLI at your deployment via `CYNC_SERVER_URL`
+(env or `~/.config/cync/config.toml`), then deploy the server + provision your
+own Supabase + R2:
+
+### 1. Provision (one time)
+- **Cloudflare R2:** create a bucket (default name `cync`) and an API token with
+  **Object Read & Write**.
+- **Supabase:** create a project, then run [`supabase/schema.sql`](supabase/schema.sql)
+  in the SQL editor. Enable **Auth → Providers → GitHub** (create a GitHub OAuth App
+  with callback `https://<ref>.supabase.co/auth/v1/callback`). Under **Auth → URL
+  Configuration**, add redirect URLs `http://127.0.0.1:8765/callback` (CLI) and
+  `http://localhost:5173/auth/callback` (web).
+
+### 2. Server
+```bash
+uv venv && source .venv/bin/activate
+uv pip install -e ".[server]"
+cp .env.example .env     # fill in R2_* and SUPABASE_* (URL, anon, service_role)
+cync-server              # http://127.0.0.1:8787
+```
+> For cross-machine use, expose the server over **HTTPS** (Tailscale, Fly.io, Railway).
+> The CLI refuses non-HTTPS server URLs except on localhost.
+
+### 3. CLI (each machine)
+```bash
+uv pip install -e .                      # base install
+export CYNC_SERVER_URL=http://127.0.0.1:8787   # or your https URL / config.toml
+cync login                               # sign in with GitHub (opens a browser)
+
+cd ~/path/to/your/project
+cync init droneforge                     # create + link a project (machine A)
+cync push
+# on machine B:  cync link droneforge && cync pull  →  claude --resume
+```
+
+### 4. Web viewer (optional)
+```bash
+cd client
+pnpm install
+cp .env.example .env   # PUBLIC_SUPABASE_URL, PUBLIC_SUPABASE_ANON_KEY, CYNC_SERVER_URL
+pnpm dev               # http://localhost:5173 → "Sign in with GitHub"
+```
+The SvelteKit server holds the token (Supabase SSR cookies); browse at `/p/<project>`.
+
+## Commands
+| Command | What it does |
+|---|---|
+| `cync login` / `logout` / `whoami` | GitHub auth session |
+| `cync init <name>` | create a project + link this directory |
+| `cync link <name>` | link this directory to an existing project |
+| `cync unlink` | remove this directory's link |
+| `cync push [id]` | upload this project's conversation(s) |
+| `cync pull [id]` | download into `~/.claude` (overwrite/add) |
+| `cync list` | list this project's conversations |
+| `cync project list` / `rm <name>` | manage your projects |
+
+## Migrating from v0.2
+If you have v0.2 (static-token) data still in R2, after `cync login`:
+```bash
+python scripts/migrate_legacy.py --slug <name> --email <your-github-email> [--purge]
+```
+Or simply re-`cync push` from a machine that has the conversations locally.
+
+## Security
+- Per-user GitHub auth (Supabase JWT); every project/conversation is owner-scoped,
+  with Postgres RLS as a backstop. The server holds R2 + Supabase keys; clients never do.
+- CLI login uses PKCE + a single-use loopback callback; the session (refresh token)
+  is stored `0600` at `~/.config/cync/session.json`.
+- Request bodies are capped (`CYNC_MAX_BODY_BYTES`, default 64 MB).
+
+## Layout
+```
+src/cync/        server (FastAPI), CLI, auth, Supabase + R2 stores
+client/          SvelteKit web viewer (GitHub login)
+supabase/        Postgres schema + RLS
+scripts/         legacy migration
+```
+
+## Limitations
+- Last-writer-wins; no version history yet.
+- Syncs the `.jsonl` transcript only (enough for `--resume`); not `todos/` sidecars.
+- Don't `push` a conversation that's open in Claude Code — quit first so it isn't mid-write.
+- Listing reads one object per conversation from Postgres (fine for personal scale).

cync_cli-0.3.0/client/.env.example

@@ -0,0 +1,3 @@
+PUBLIC_SUPABASE_URL=https://<ref>.supabase.co
+PUBLIC_SUPABASE_ANON_KEY=your_supabase_anon_key
+CYNC_SERVER_URL=http://127.0.0.1:8787

cync_cli-0.3.0/client/.gitignore

@@ -0,0 +1,23 @@
+node_modules
+
+# Output
+.output
+.vercel
+.netlify
+.wrangler
+/.svelte-kit
+/build
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Env
+.env
+.env.*
+!.env.example
+!.env.test
+
+# Vite
+vite.config.js.timestamp-*
+vite.config.ts.timestamp-*

cync_cli-0.3.0/client/.npmrc

@@ -0,0 +1 @@
+engine-strict=true

cync_cli-0.3.0/client/.vscode/extensions.json

@@ -0,0 +1,3 @@
+{
+	"recommendations": ["svelte.svelte-vscode"]
+}

cync_cli-0.3.0/client/README.md

@@ -0,0 +1,29 @@
+# cync-viewer
+
+A small read-only SvelteKit app to browse Claude Code conversations synced by
+[cync](../). The SvelteKit server proxies to the cync API and injects the bearer
+token server-side, so the token never reaches the browser.
+
+## Setup
+
+```sh
+pnpm install
+cp .env.example .env   # set CYNC_SERVER_URL and the same CYNC_TOKEN as the server
+```
+
+## Develop
+
+```sh
+pnpm dev               # http://localhost:5173
+```
+
+## Build
+
+```sh
+pnpm build
+pnpm preview
+```
+
+> This project uses **pnpm** (see `pnpm-lock.yaml`); avoid mixing in `npm install`.
+> For a real deployment, replace `@sveltejs/adapter-auto` with a pinned adapter
+> such as `@sveltejs/adapter-node`.

cync_cli-0.3.0/client/package.json

@@ -0,0 +1,28 @@
+{
+	"name": "cync-viewer",
+	"private": true,
+	"version": "0.0.1",
+	"type": "module",
+	"scripts": {
+		"dev": "vite dev",
+		"build": "vite build",
+		"preview": "vite preview",
+		"prepare": "svelte-kit sync || echo ''",
+		"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
+		"check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch"
+	},
+	"devDependencies": {
+		"@sveltejs/adapter-vercel": "^6.3.4",
+		"@sveltejs/kit": "^2.63.0",
+		"@sveltejs/vite-plugin-svelte": "^7.1.2",
+		"@types/node": "^26.0.1",
+		"svelte": "^5.56.1",
+		"svelte-check": "^4.6.0",
+		"typescript": "^6.0.3",
+		"vite": "^8.0.16"
+	},
+	"dependencies": {
+		"@supabase/ssr": "^0.12.0",
+		"@supabase/supabase-js": "^2.109.0"
+	}
+}