Check against your doze
Checking against doze
doze
OfficialSignedThe doze maintainers. Every module in the registry today is published and signed here, built in public CI from source on GitHub.
8 modules
No download counts: doze sends nothing home, so the registry has nothing to count. Dates are when each release was built on GitHub.
| Logo | Module | Newest release | Runs | Releases | Source |
|---|---|---|---|---|---|
| PostgreSQL doze/postgres Real Postgres, declared not scripted: roles, schemas, grants and extensions. | 0.2.4 · 2 Nov 2026 any doze | Postgres 14 – 18 | |||
| FerretDB doze/ferret MongoDB-compatible: any Mongo client connects. FerretDB 2 over a private Postgres. | 0.2.3 · 2 Nov 2026 any doze | FerretDB 2 | |||
| Temporal doze/temporal A local Temporal dev server with its Web UI. One Go binary, SQLite store. | 0.2.2 · 4 Jul 2026 any doze | Temporal CLI 1.x | |||
| Valkey doze/valkey In-memory cache that speaks the Redis protocol: any redis client works. | 0.2.1 · 2 Jul 2026 any doze | Valkey 8 – 9 | |||
| Kvrocks doze/kvrocks The Redis protocol on RocksDB: durable, and the data lives on disk, not in RAM. | 0.2.1 · 2 Jul 2026 any doze | Kvrocks 2 | |||
| MariaDB doze/mariadb MySQL-compatible. Databases, users and grants declared in doze.hcl. | 0.2.1 · 2 Jul 2026 any doze | MariaDB 11 | |||
| Kafka doze/kafka doze Kafka: a Kafka-protocol broker in one Go binary. No JVM, no ZooKeeper, no KRaft. | 0.1.2 · [date] any doze | itself · Kafka protocol 1 – 4 | |||
| AWS doze/aws doze AWS as one service: S3, SQS, DynamoDB, Lambda and 13 more on one endpoint, with its console. | 0.2.0 · [date] needs doze 0.2.0 | itself: doze AWS is in the module |
Releases counts what the signed index serves. One modules' newest releases need doze 0.2.0; an older doze skips them and keeps resolving the release before. PostgreSQL 0.2.4, FerretDB 0.2.3, Temporal 0.2.2, Valkey 0.2.1, Kvrocks 0.2.1, MariaDB 0.2.1 and doze Kafka 0.1.2 run on any doze.
How it is verified
Three separate proofs that this namespace belongs to the people who make doze.
Key compiled into doze
The namespace key is a constant in doze's own source. Every doze binary checks against it.
Source in the doze-dev GitHub org
Modules build from doze-modules, doze AWS and doze Kafka; signing runs in doze-registry.
Domain doze-dev.com
A DNS TXT record on the domain names the key, so anyone can check the namespace and the website share an owner.
_doze-registry.doze-dev.com TXT "ed25519=Nu5y8mbjYv7XEtNFBXwPVl+C8SBteVApIROefBwGWjw="[Record name and format to decide.]
Key history
Nu5y8mbjYv7XEtNFBXwPVl+C8SBteVApIROefBwGWjw=- 26 Jun 2026. Namespace renamed from nerdmenot to doze and a new key generated, before the first doze release (2 Jul). Nothing signed by the old key is served.
- No rotations since. See the rotation policy (still open).
Owned by the doze-dev GitHub org since 26 Jun 2026. No past owners. [The list of people who can approve a release is to be shown here.]
Notices
No key changes, advisories, yanked releases or deprecations from this publisher.
A notice is a dated, plain-text warning shown here and on every affected release page: a key rotation, a security advisory, a yanked release, a module or engine major being deprecated.