Auth.js CLI

Why it's ranked here

Its strongest workflows remove error-prone setup work: generating secrets, calculating callback URLs, collecting provider credentials, and updating environment files. The verdict is mixed because ordinary project scaffolding is explicitly unfinished, while provider guidance covers only entries with setup instructions.

What's good

It detects Next.js, Express, and SvelteKit projects before changing configuration. Provider setup copies the callback URL, opens the provider console, masks secret input, and asks before overwriting existing environment values. Secret generation can write the framework-specific environment file or print raw output.

Tradeoffs

Normal project scaffolding stops with an explicit not-implemented error, so initialization currently depends on cloning a full example. Provider metadata is broad, but guided credential setup is available only where a setup URL exists. Documentation questions require the external Inkeep AI service and network access.

How to use it well

Use it when starting from an official example or adding supported OAuth credentials and secrets to an existing Next.js, Express, or SvelteKit project. It suits interactive local setup and quick documentation questions. Do not treat it as a complete framework generator or universal provider configurator.

Observed

License

MIT

Primary language

JavaScript using ECMAScript modules

Packaging

npm package named auth with an auth executable

Install surface

Runs through npx, pnpx, bunx, or yarn dlx without permanent installation

Interface

CLI with ask, init, secret, and add commands

Runtime

Node.js 18 or newer

Framework support

Next.js, Express, and SvelteKit