damatjs/user
v0.2.0VerifiedAuthentication, sessions and accounts — drop-in users, credentials, and session management for any Damat app.
Install
$ damat module add damatjs/user@0.2.0
Pin a version with @version (see the table below), or read the installing modules guide.
What happens when you install
- 1ResolveThe ref damatjs/user is looked up in this registry's index and mapped to its pinned source.
- 2VerifyThe owner and verification status are checked against your DAMAT_MODULE_VERIFY policy.
- 3CopyThe module lands in src/modules/user — models, service, config, migrations, and workflows.
- 4WireIt is registered in damat.config.ts under the "user" id, and its env keys are synced to .env.example.
- 5MigrateYou apply its schema with `bun damat-orm migrate:up`, then restart the dev server.
Versions
| Version | Pinned source | Install |
|---|---|---|
| 0.2.0latest | https://github.com/damatjs/modules.git#user-v0.2.0 | damat module add damatjs/user@0.2.0 |
| 0.1.0 | https://github.com/damatjs/modules.git#user-v0.1.0 | damat module add damatjs/user@0.1.0 |
Trust & verification
verifiedby registry.damatjs.com
Reviewed by the registry — the source is pinned and the owner is confirmed. Installs cleanly under every policy.
Your install gate — DAMAT_MODULE_VERIFY
- off
- install anything the registry serves
- warn (default)
- install, but print what you are trusting
- require
- only verified entries install
Agents
Install it from an AI agent
Point the Damat MCP server at this registry and your assistant can discover, inspect, and install this module for you.
.mcp.json
{
"mcpServers": {
"damat-modules": {
"command": "bunx",
"args": ["damat-mcp"],
"env": { "DAMAT_MODULE_REGISTRY": "https://registry.damatjs.com/index.json" }
}
}
}“Install the damatjs/user module into my app and tell me what to run next.”
Set up the module MCP →