Check against your doze

Valkey

OfficialSigned

In-memory cache, Redis-compatible.

doze/valkey

$ doze add valkey

Newest: 0.2.1 · 2 Jul 2026
Needs: any doze
Runs: Valkey 8 – 9
Platforms: macOS arm64 · Linux arm64 · Linux x86_64
Licence: Apache-2.0
Source: doze-modules

valkey 0.2.1

Current

Release

Released: 2 Jul 2026
Needs: any doze
Plugin protocol: 1
Engines: Valkey 8–9
Platforms: 3 of 3
Advisories: None known

0.2.1 sets no oldest doze, so it runs on every doze (0.1.0 and up).

Release notes

View on GitHub

No notes for this release.

Artifacts

One signed archive per platform. Files live on GitHub; the registry lists them and signs their checksums.

Platform	File (downloads from GitHub)	SHA-256	Signature (ed25519)
macOS arm64 aarch64-apple-darwin	valkey-plugin-0.2.1-aarch64-apple-darwin.tar.gz	`4d4ccc27eafeced61dc6597fb9089fac8ab64803dbf4d67e01f98fc52e987f13`	`uY6lh8M7…X5Bw==`
Linux arm64 aarch64-unknown-linux-gnu	valkey-plugin-0.2.1-aarch64-unknown-linux-gnu.tar.gz	`f800301cfc0427474587d20cbee3387613593dda3cfc7819e9961e4b0f6a42b4`	`zaCQ/dLp…nFBA==`
Linux x86_64 x86_64-unknown-linux-gnu	valkey-plugin-0.2.1-x86_64-unknown-linux-gnu.tar.gz	`d06d41ea23051a8310dee5ad94bce2c6c06f0912c9bf3360fd73402d2fdac458`	`nuajeQjI…4GAg==`

Every file is under https://github.com/doze-dev/doze-modules/releases/download/valkey/. Intel Macs and Windows have no build; WSL2 uses the Linux x86_64 file.

Signing

The index is signed as a whole, and each archive is signed. doze checks both before anything runs, and refuses a module whose checksum or signature doesn't match.

Key: Nu5y8mbj…Wjw=
Where the key lives: Compiled into doze. doze never fetches or trusts a key on first use.
Namespace: doze
Publisher: doze-dev Official
Index signature: vGTQgqEU…BA==
What is signed: Each archive: its lowercase-hex SHA-256. The index: module, namespace, releases and channels as canonical JSON.
Not yet signed: The doze (oldest doze) field sits beside the signed part today. new The design moves it inside.

How signing works

Verify it yourself

[planned: doze modules verify] Today doze runs these checks itself on every download. The same checks by hand, for macOS arm64. Needs OpenSSL 3: the openssl that ships with macOS has no ed25519 (brew install openssl@3).

Checksum, then signature

# 1. download and hash; compare with the table above
$ curl -LO https://github.com/doze-dev/doze-modules/releases/download/valkey/valkey-plugin-0.2.1-aarch64-apple-darwin.tar.gz
$ shasum -a 256 valkey-plugin-0.2.1-aarch64-apple-darwin.tar.gz
4d4ccc27eafeced61dc6597fb9089fac8ab64803dbf4d67e01f98fc52e987f13  valkey-plugin-0.2.1-aarch64-apple-darwin.tar.gz

# 2. the signature is over that hex string, with doze's public key
$ printf %s 4d4ccc27eafeced61dc6597fb9089fac8ab64803dbf4d67e01f98fc52e987f13 > digest.txt
$ echo 'uY6lh8M7itDev/qNBD9GOwwASYNUYBeSr8UbolAXvWu5NvGJ/YAgjdyBetil7mtkOhZmRLMm4HSuP1IJ8SX5Bw==' | base64 -d > sig.bin
$ (printf '\x30\x2a\x30\x05\x06\x03\x2b\x65\x70\x03\x21\x00'; echo 'Nu5y8mbjYv7XEtNFBXwPVl+C8SBteVApIROefBwGWjw=' | base64 -d) > doze-key.der
$ openssl pkeyutl -verify -pubin -keyform DER -inkey doze-key.der -rawin -in digest.txt -sigfile sig.bin
Signature Verified Successfully

What doze.lock records for 0.2.1

A project pinned to 0.2.1 carries this entry. Every platform's checksum goes in, so a teammate on Linux verifies against the same pin you made on a Mac. Pinned and cached means no network at all.

The engine itself is pinned separately, under engines:. Engine versions

doze.lock

modules:
    doze/valkey:
        version: 0.2.1
        protocol: 1
        engines:
            - "8"
            - "9"
        hashes:
            aarch64-apple-darwin: sha256:4d4ccc27eafeced61dc6597fb9089fac8ab64803dbf4d67e01f98fc52e987f13
            aarch64-unknown-linux-gnu: sha256:f800301cfc0427474587d20cbee3387613593dda3cfc7819e9961e4b0f6a42b4
            x86_64-unknown-linux-gnu: sha256:d06d41ea23051a8310dee5ad94bce2c6c06f0912c9bf3360fd73402d2fdac458
        # no doze: line; 0.2.1 sets no oldest doze