Read 2026-10-04
dgtlmoon/changedetection.io: technical due diligence, read from its repository
What Borehole read in dgtlmoon/changedetection.io's code and history at 0e05667: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongchangedetectionio/flask_app.py is 1,863 lines, 13× this codebase's median file
adequateThe median source file here is 138 lines. 2 files exceed 1,380 lines, the largest being 1,863. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
changedetectionio/flask_app.py:1 — 1,863 lines (13× median) |
changedetectionio/forms.py:1 — 1,433 lines (10× median) |
80 errors caught and discarded in product code
adequate80 places catch an error and do nothing with it, across 35 files (0.8 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
changedetectionio/__init__.py:77 — error caught and discarded |
changedetectionio/blueprint/imports/importer.py:139 — error caught and discarded |
changedetectionio/blueprint/imports/importer.py:141 — error caught and discarded |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate57 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
changedetectionio/static/styles/package.json:7 — >=18.0.0 |
changedetectionio/static/styles/package.json:16 — ^1.77.8 |
docs/package.json:10 — ^1.34.5 |
requirements.txt:1 — ~=1.0 |
requirements.txt:2 — ~=6.0 |
1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate6 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/containers.yml:69 — action pinned by tag |
.github/workflows/containers.yml:75 — action pinned by tag |
16 advisories against this project in the last 24 months, 10 high or critical
adequateThe newest was published on 2026-08-20. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 2 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.60.8. Answer lives in: the release you run, set against each fixed version.
| 2026-08-20: GHSA-gwph-fp79-379w (high), fixed in 0.56.1: changedetection.io SSRF protection bypass via CGNAT addresses |
| 2026-04-27: GHSA-8757-69j2-hx56 (high), fixed in 0.55.1: Arbitrary Local File Read via crafted backup restore |
| 2026-04-27: GHSA-v7cp-2cx9-x793 (moderate): # changedetection.io_XXE_01 Vulnerability Report: We discovered a XXE vulnerability in the changedetection.io project |
| 2026-04-04: GHSA-jmrh-xmgh-x9j4 (critical), fixed in 0.54.8: Authentication Bypass via Decorator Ordering |
| 2026-03-26: GHSA-58r7-4wr5-hfx8 (high), fixed in 0.54.7: Environment Variable Disclosure via jq env Builtin in Include Filters |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 468 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 468 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 468 files for 10 structured logging libraries; 0 matched |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
1 of 1 deployed images carry no version, or `latest`
adequate1 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker-compose.yml:3 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on dgtlmoon/changedetection.io: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.