readystack/vaultwarden repository overview

⁠Vaultwarden

readystack/vaultwarden:1.37.4-CE-ubuntu24.04-r4

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/vaultwarden/recipe⁠
• Upstream source at this release's pinned commit (1.37.4): https://github.com/dani-garcia/vaultwarden/tree/7c188967e7a467b19b2757bc3326f9cf3ccae327⁠
• Product page: https://readystack.dev/products/vaultwarden⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/vaultwarden⁠
• Release history (JSON): https://readystack.dev/api/releases/vaultwarden⁠
• Defect record: https://readystack.dev/defects.html?product=vaultwarden⁠
• Today's scan: https://readystack.dev/products/vaultwarden#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=vaultwarden⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/dani-garcia/vaultwarden 1.37.4 (AGPL-3.0-only), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Families, small teams and self-hosters who want a password manager whose server they run themselves.

Why: Vaultwarden is a lightweight, self-hosted password manager server. It implements another password manager's client API, so that manager's existing browser, desktop and mobile apps connect to it.

Use case: A small office wants shared passwords out of spreadsheets. On Vaultwarden each person has a personal vault, the team shares logins through an organisation with collections, and everyone signs in with two-factor authentication from the apps they already use.

About the upstream project, written from its own description: https://github.com/dani-garcia/vaultwarden⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:8d1f0c0716f7a5da2620f2862272a7baf1874e586a82170665e3447314c282dd on 2026-10-28.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/vaultwarden⁠
• ReadyStack release check — passed at release on 2026-10-27: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:8d1f0c0716f7a5da2620f2862272a7baf1874e586a82170665e3447314c282dd; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/vaultwarden:1.37.4-CE-ubuntu24.04-r4.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (vaultwarden).
• Built from source by ReadyStack; the web UI in /web-vault is upstream's prebuilt release https://github.com/dani-garcia/bw_web_builds/releases/download/v2026.7.0/bw_web_v2026.7.0.tar.gz⁠ (sha256 002e972bf0d0…).

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 1.37.4-CE-ubuntu24.04-r4 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/vaultwarden:1.37.4-CE-ubuntu24.04-r4

# ✗ unsupported (do not pull)
docker pull readystack/vaultwarden:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/vaultwarden:1.37.4-CE-ubuntu24.04-r4 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container. A Rust (Rocket) server binary (~40MB ELF, dynamically linked against Ubuntu 24.04's OpenSSL 3.0, package libssl3t64) with embedded SQLite statically compiled in. Serves a PREBUILT Bitwarden-compatible web vault UI from /web-vault on disk. NO external database (self-managed SQLite under /data). The image IS the complete running instance (no docker-compose, no Kubernetes, no DB sidecar).

docker run -d --name vaultwarden -p 8080:8080 -e DOMAIN=https://vault.YOURDOMAIN.tld -v vw-data:/data readystack/vaultwarden:1.37.4-CE-ubuntu24.04-r4

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/vaultwarden⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:5a333ebba93eb24b0fd0812ca9f7fe5728b9f7b5c383fa6edc13fe217c6d323f on 2026-10-28.

— ReadyStack · readystack.dev