Oxy Examples

Standalone Next.js, Vite, and Expo reference applications. Each directory has its own manifest and Bun lockfile and can be copied independently.

Starter	Integration	Status
Next.js	Published OxyProvider + OxySignInButton	Frozen install, types and production build verified
Vite	Same public provider and button	Frozen install, types and production build verified
Expo	Published provider and shared native OAuth completion	Frozen install, types and web export verified; native development build required for device testing

All three starters pin registry-published services 13.0.0, core 7.1.0, contracts 6.0.0 and Bloom 15.11.0. Protocol 1.5.1 is resolved transitively. The source consumes registry packages without local aliases or SDK forks. The starters use the published Expo/native peers required by the SDK. Each .env.example documents the API URL, registered public client ID, and exact registered return URI. Fill the client ID before building. The examples are external third_party apps: ordinary OAuth + PKCE and consent apply regardless of their Oxy name. No new registry records or real credentials are created by this repository.

The SDK owns sign-in, the callback, and session state. Starters do not contain local token plumbing or sign-in screens. Local fixture/browser checks are maintained separately from the starters; there is no added test framework. These checks do not prove live SSO, production deployment, or provider grants.

See SDK13 adoption for the current checks. Earlier registry verification records the previous package hashes and build limits. The earlier verification/ record preserves the old SDK's logout regression; it does not describe the currently pinned release.

Formatting and linting

One root Biome config covers all three starters. Run it from the repository root (CI runs bunx @biomejs/biome@2.5.15 ci . on every pull request):

bunx @biomejs/biome@2.5.15 check .          # lint + format check
bunx @biomejs/biome@2.5.15 check --write .  # apply safe fixes and formatting
bunx @biomejs/biome@2.5.15 format --write . # format only

There is deliberately no root package.json or lockfile: a root bun.lock would make Next.js treat the repository root as its workspace root. In the Expo starter, a Biome plugin (biome-plugins/expo-env-vars.grit) rejects destructured or computed process.env reads, which Metro does not inline. When you copy a starter out of this repository, copy biome.json (and the plugin, for Expo) along with it if you want the same checks.

Platform repository · Third-party integration contracts

These starters remain third-party OAuth applications. Register their exact redirect URI and requested scopes in Oxy; external consent, scope limits and grant revocation still apply. The own-app scope-free contract does not turn a starter into an Oxy-owned application. No client secret or trusted-origin override belongs in these bundles.