readystack/changedetection repository overview

⁠changedetection.io

readystack/changedetection:0.60.10-CE-ubuntu24.04-r1

Source, recipe and records

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

A cosign-signed build of github.com/dgtlmoon/changedetection.io 0.60.10 (Apache-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: People and teams who watch web pages for changes to prices, stock levels, job listings or policies.

Why: changedetection.io checks web pages on a schedule you set, can watch only the part of a page you choose, and sends a notification when that content changes.

Use case: A small shop tracks the prices its suppliers publish. changedetection.io checks each supplier page during business hours, watches only the price element picked with a CSS selector, and sends an email or webhook when it changes, so nobody has to reload the pages by hand.

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

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:38dfa7fa7bc63368e9c380cc03cd60c2d5cef0a46fd3e3df941cc70cfde34846 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/changedetection⁠
• ReadyStack release check — passed at release on 2026-10-28: 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:38dfa7fa7bc63368e9c380cc03cd60c2d5cef0a46fd3e3df941cc70cfde34846; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/changedetection:0.60.10-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (changedetection).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 0.60.10-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/changedetection:0.60.10-CE-ubuntu24.04-r1

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

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/changedetection:0.60.10-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. A Python (Flask) self-hosted web-page change-monitoring + notification service. State is JSON (changedetection.json/watch.json) + text history snapshots (brotli-compressed when larger than 20 KB) under /datastore — there is NO SQL database. The image IS the complete running instance (no external DB, no sidecar). The default html_requests fetcher (plain HTTP requests) is the only fetcher that works in this hermetic CE image: Playwright is not installed, and the WebDriver Chrome/Javascript fetch method that the UI offers fails every check with No module named 'PIL', even with a WebDriver server set in WEBDRIVER_URL.

docker run -d --name changedetection -p 5000:5000 -v changedetection-data:/datastore readystack/changedetection:0.60.10-CE-ubuntu24.04-r1

⁠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/changedetection⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:99092a0c9ffe8f4371f53957c083fb32d64e0070e40a13d55cd21d9a4fb38437 on 2026-10-28.

— ReadyStack · readystack.dev