@zixcel/github-auth

Add GitHub Device Flow to an application using an explicit public client registration.

What you can do

• Present the device authorization steps.
• Track polling, expiry and authorization results.

Current scope

The application owns client registration, presentation and credential custody. This package does not retain a user token as repository content.

Package distribution is not activated by this documentation. Use the checked-in source and the declared dependency versions; published availability must be verified separately.

Getting started

Use [email protected] and the Node.js version declared in engines in package.json. Run from this repository:

pnpm install --frozen-lockfile
pnpm test

Integration example

import { githubAuthDeclaration, requestGitHubDeviceCode }
  from '@zixcel/github-auth'

const declaration = githubAuthDeclaration()
const attempt = await requestGitHubDeviceCode(declaration,
  { clientId: 'Iv23Public', nowUnixMs: Date.now() }, transport)

Documentation and source

Interface reference

Usage guide

Schemas · Implementation and public interfaces · Verification cases · Contributing · Security reporting · License · Attribution notices

Typed development

Use Node 24.15 or later and pnpm 10.29.3. Contract types are in src/types. Runtime validation, provider wire handling and custody challenge validation have separate modules. Executable ESM and declarations are generated together in dist.

pnpm install --frozen-lockfile --ignore-scripts --config.auto-install-peers=false
pnpm run typecheck
pnpm test
pnpm pack

Tests inject synthetic transport and custody ports; they do not access a real GitHub account. A pending provider response never establishes a connection. The custody verifier owns challenge expiry and user-proof validation before issuing a connection receipt.