@krizaka/auth
What it is — Accounts and roles: profile, e-mail change by link, password, sessions, roles as data.
Krizaka TS · open source
The TypeScript backend building blocks behind every Krizaka product
Accounts, settings, API keys, webhooks — written once, tested on a real PostgreSQL, published on npm. A product installs a package and writes only what is its own.
npm install @krizaka/auth @krizaka/settings @krizaka/api-keys @krizaka/webhooks @krizaka/organize @krizaka/brief- 6
- packages on npm
- 155
- exported names
- Apache-2.0
- licence
- Node >=22
- runtime
Why
One implementation, no copies
What every product used to rewrite lives in one place, with one author and one release.
Ports, not frameworks
No framework, no vendor SDK, no environment variable, no ambient clock: a package asks for a store, a mailer, a clock — you pass them in.
Tested on the real thing
Where a package stores, its integration test runs on PostgreSQL, and a store ships a contract kit that every adapter runs.
Versioned, published, readable
Each package has its own version and changelog (Changesets) on npm; this site is generated from the same files, at every change.
Packages
6 packages, one npm scope
Each page has the install command, the README, every exported name and the changelog.
@krizaka/settings
What it is — Configuration as data: a typed registry, user over workspace over global, every change audited.
@krizaka/api-keys
What it is — API keys created, rotated, revoked and authenticated; shown once, only a hash kept.
@krizaka/webhooks
What it is — Signed, idempotent webhooks, both ways: delivered with retries, verified and applied once.
@krizaka/organize
What it is — A name, an avatar, tags and collections for any entity, with a conformance kit.
@krizaka/brief
What it is — The weekly brief: a few figured recommendations, each with one action.
Install a package
From an empty project to an account, a settings registry or signed webhooks — one package at a time.