readystack/homeassistant repository overview

⁠Home Assistant

readystack/homeassistant:2026.11.1-CE-ubuntu24.04-r2

Source, recipe and records

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

A cosign-signed build of github.com/home-assistant/core 2026.11.1 (Apache-2.0), built clean-room from upstream's published release artifact by ReadyStack⁠.

⁠Who uses it and why

Who: Home owners, tinkerers and DIY enthusiasts who want to automate their homes with local control and privacy.

Why: Home Assistant is open-source home automation. It brings devices from many makers together through integrations and runs automations locally, on a small computer or server at home.

Use case: A household has smart plugs, motion sensors and a thermostat from different makers, each with its own app. Home Assistant brings them into one dashboard and runs automations such as switching off the lights when everyone has left, on a local server, so the home's data stays in the house.

About the upstream project, written from its own description: https://github.com/home-assistant/core⁠ · https://www.home-assistant.io/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:c13e2254904b69d9b9fed56124186f815b78f4e1e7e8ffafa381bdb94c801ec7 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/homeassistant⁠
• ReadyStack release check — passed at release on 2026-11-12: 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:c13e2254904b69d9b9fed56124186f815b78f4e1e7e8ffafa381bdb94c801ec7; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/homeassistant:2026.11.1-CE-ubuntu24.04-r2.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (homeassistant).
• Built from upstream's published release artifact (https://pypi.org/project/homeassistant/2026.11.1/⁠) by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 2026.11.1-CE-ubuntu24.04-r2 — 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/homeassistant:2026.11.1-CE-ubuntu24.04-r2

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

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

⁠Deployment

Single container running Home Assistant Core in the foreground against a self-contained SQLite recorder database. This is Home Assistant CORE — not Home Assistant OS and not the Supervisor, so there are no add-ons and no supervisor-managed updates.

docker run -d --name homeassistant -p 8123:8123 -v ha-config:/config readystack/homeassistant:2026.11.1-CE-ubuntu24.04-r2

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

— ReadyStack · readystack.dev