damatjs/user
v0.2.0VerifiedAuthentication, sessions and accounts — drop-in users, credentials, and session management for any Damat app.
- auth
- users
- sessions
- accounts
$ damat module add damatjs/user@0.2.0
Module registry
Backends, one module at a time.
Every entry below comes from the live registry index — the same file the CLI and MCP server resolve against. Verified entries are vouched for by registry.damatjs.com; community entries install just the same.
billing
v0.1.0CommunityStripe subscriptions and one-time credits — plans, checkout, webhooks, and a credits ledger.
- stripe
- payments
- subscriptions
- credits
$ damat module add billing@0.1.0
Three ways to install
The registry is the shared catalog, but it is never a gatekeeper — a module is just a git repo or a folder that follows the module contract.
Registry name
Resolved through the registry index — entries carry an owner, a version list, and a verification status.
$ damat module add damatjs/user@0.2.0
Git URL
Install straight from any git repository, pinned to a branch or tag. No registry entry required.
$ damat module add https://github.com/acme/damat-modules.git#billing-v0.1.0
Local path
Point at a module on disk while you develop it — the fastest authoring loop.
$ damat module add ../my-module
Publish your own
A module is a single self-contained feature you can build and test in isolation, then share from any git repo.
- 1
Scaffold
damat module init creates a standalone module package — models, service, config, migrations — that builds and tests on its own.
- 2
Publish
Push it to any git repository and tag a version. That repo is the distribution — there is nothing else to upload.
- 3
List it
Open a pull request adding your entry to the registry index so anyone can install it by name.
The authoring guide walks through the module contract end to end — naming, models, migrations, workflows, and validation.
Read the authoring guideBrowse the registryOpen a registry PR