readystack/metabase repository overview

⁠Metabase

readystack/metabase:v0.65.4.1-CE-ubuntu24.04-r1

Source, recipe and records

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

A cosign-signed build of github.com/metabase/metabase v0.65.4.1 (Community/OSS edition; AGPL-3.0 — all source outside the upstream enterprise/ directory, which is the Commercial-License EE edition and is removed before the build), built clean-room from official upstream source, with the source changes listed below by ReadyStack⁠.

⁠Who uses it and why

Who: Companies that want everyone, not only analysts, to ask questions of their data.

Why: Metabase is an open-source business intelligence tool. People explore data and build charts and dashboards without knowing SQL, and analysts use its SQL editor for more complex queries.

Use case: A start-up's product data sits in its application database and only engineers can query it. With Metabase connected to that database, the support lead charts tickets per customer without writing SQL, and the finance team gets a dashboard with filters it checks each week.

About the upstream project, written from its own description: https://github.com/metabase/metabase⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:758342c30947d9303c5bddccca1c02f28fb4eb546b953d66a6aa9481a77296ef on 2026-11-12.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v2, ce.rodeo's current rubric; scans before 2026-11-08 used cerodeo-v1) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/metabase⁠
• ReadyStack release check — passed at release on 2026-11-11: 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:758342c30947d9303c5bddccca1c02f28fb4eb546b953d66a6aa9481a77296ef; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/metabase:v0.65.4.1-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (metabase).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v0.65.4.1-CE-ubuntu24.04-r1 — 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/metabase:v0.65.4.1-CE-ubuntu24.04-r1

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

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

⁠Deployment

Single container, SELF-CONTAINED. A JVM (Clojure) business-intelligence / analytics server (dashboards, 'questions', SQL editor) shipped as one self-contained uberjar (metabase.jar) on an eclipse-temurin 25 JRE. The application database defaults to an EMBEDDED H2 file the container creates + Liquibase-migrates itself on first boot — the image IS the complete running instance (NO external DB, NO sidecar, NO docker-compose required). For production scale Metabase can OPTIONALLY be pointed at an external PostgreSQL/MySQL application database via MB_DB_TYPE + MB_DB_* env vars, but that is optional; the default and certified single-container posture is embedded H2, but Metabase logs a warning at every start that H2 is not recommended for production, so back up /metabase-data regularly.

docker run -d --name metabase -p 3000:3000 -v metabase-data:/metabase-data readystack/metabase:v0.65.4.1-CE-ubuntu24.04-r1

⁠Source changes (AGPL)

This software is licensed under the GNU Affero General Public License, and the releases below are built from a modified copy of its source. Each line names a release, what ReadyStack changed and where the diff is published. From 2026-10-27 a release's diff carries every upstream file its build changes, the dependency manifests and lockfiles included, so its complete corresponding source is the upstream tag with that diff applied; the diff of an earlier release carries the source edits its line names, and the dependency files that release's build changed are in its release archive (vendored/). If you let users interact with the server over a network, AGPL-3.0 section 13 asks you to offer them its source; for a release from 2026-10-27 on, a link to its diff and the upstream tag does that.

• v0.65.4.1-CE-ubuntu24.04-r1 — shadow-cljs.edn compiles the ClojureScript frontend serially (:parallel-build false) and loads ReadyStack's build-time JSChunk name-hash agent through :jvm-opts, so the frontend bundle reproduces; deps.edn is not changed; full diff at https://readystack.dev/source/metabase/v0.65.4.1/metabase-v0.65.4.1-readystack.patch⁠
• v0.65.3.7-CE-ubuntu24.04-r1 — shadow-cljs.edn compiles the ClojureScript frontend serially (:parallel-build false) and loads ReadyStack's build-time JSChunk name-hash agent through :jvm-opts, so the frontend bundle reproduces; deps.edn is not changed; full diff at https://readystack.dev/source/metabase/v0.65.3.7/metabase-v0.65.3.7-readystack.patch⁠
• v0.65.3.6-CE-ubuntu24.04-r1 — shadow-cljs.edn compiles the ClojureScript frontend serially (:parallel-build false) and loads ReadyStack's build-time JSChunk name-hash agent through :jvm-opts, so the frontend bundle reproduces; deps.edn is not changed; full diff at https://readystack.dev/source/metabase/v0.65.3.6/metabase-v0.65.3.6-readystack.patch⁠
• v0.64.3.5-CE-ubuntu24.04-r1 — shadow-cljs.edn compiles the ClojureScript frontend serially (:parallel-build false) and loads ReadyStack's build-time JSChunk name-hash agent through :jvm-opts, so the frontend bundle reproduces; deps.edn adds two top-level dependency floors for security fixes (at.yawk.lz4/lz4-java 1.11.4, io.netty/netty-codec-dns 4.1.136.Final); full diff at https://readystack.dev/source/metabase/v0.64.3.5/metabase-v0.64.3.5-readystack.patch⁠
• v0.64.3-CE-ubuntu24.04-r1 — shadow-cljs.edn compiles the ClojureScript frontend serially (:parallel-build false) and loads ReadyStack's build-time JSChunk name-hash agent through :jvm-opts, so the frontend bundle reproduces; deps.edn adds two top-level dependency floors for security fixes (at.yawk.lz4/lz4-java 1.11.4, io.netty/netty-codec-dns 4.1.136.Final); full diff at https://readystack.dev/source/metabase/v0.64.3/metabase-v0.64.3-readystack.patch⁠

⁠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/metabase⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:6c587fce29aec80301f10e28952268e068a371dae76137f1b078fee9fa74c1ae on 2026-11-11.

— ReadyStack · readystack.dev