Read 2026-10-23
dagucloud/dagu: technical due diligence, read from its repository
What Borehole read in dagucloud/dagu's code and history at f609cae: 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 | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongui/src/api/v1/schema.ts is 22,867 lines, 150× this codebase's median file
adequateThe median source file here is 152 lines. 28 files exceed 1,520 lines, the largest being 22,867. 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.
ui/src/api/v1/schema.ts:1 — 22,867 lines (150× median) |
ui/src/i18n/staticMessages.ts:1 — 7,861 lines (51× median) |
internal/service/frontend/api/v1/dagruns.go:1 — 5,325 lines (35× median) |
internal/service/coordinator/handler.go:1 — 3,832 lines (25× median) |
internal/gitsync/service.go:1 — 3,477 lines (22× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (ui/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
ui/playwright.config.ts:46 — test retry |
13% of recent commits change more than 2,000 lines
adequate267 of 2026 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 267 commits over 2,000 lines |
Product & Engineering Maturity
adequate104 direct dependencies in a single manifest
adequatego.mod declares 104 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
go.mod — 104 declared |
ui/package.json — 49 declared |
npm/dagu/package.json — 1 declared |
Security & Reliability Posture
adequate1 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 |
34 locked dependencies have published vulnerabilities, 29 high or critical in what ships
adequate34 of 1,870 locked dependencies match 130 published advisories in OSV, 56 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.
ui/pnpm-lock.yaml — shell-quote 1.10.0: GHSA-pqg4-j6r4-53mv (critical), fixed in 1.11.0 |
ui/pnpm-lock.yaml — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8; a development dependency |
ui/pnpm-lock.yaml — @vue/server-renderer 3.5.29: GHSA-g2v6-rqmx-r4w6 (high), fixed in 3.5.42 |
5 places insert HTML from a variable without sanitising it
adequate5 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
ui/src/assets/js/prism.js:3 — HTML from a variable |
ui/src/assets/js/prism.js:6 — HTML from a variable |
ui/src/components/ui/mermaid-block.tsx:78 — HTML from a variable |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
ui/webpack.dev.js:9 — source maps in a production build |
6 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-07-26. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 4 records name dagu with nothing tying them to this repository (CVE-2026-27598, CVE-2026-31882, CVE-2026-31886, …).
| 2026-07-26: GHSA-5m6c-38r8-5w76 (moderate), fixed in v2.11.0: Incomplete fix of CVE-2026-33344 - the traversal guard is HTTP-only middleware, but the MCP service calls GetDAGSpec in-process, so arbitrary .yaml/.yml file re |
| 2026-03-19: GHSA-ph8x-4jfv-v9v8 (high), fixed in v2.3.1: Incomplete fix for CVE-2026-27598: path traversal via %2F-encoded slashes in locateDAG |
| 2026-03-13: GHSA-9wmw-9wph-2vwp (high): SSE Authentication Bypass in Basic Auth Mode |
| 2026-03-13: GHSA-m4q3-457p-hh2x (critical): Path Traversal via `dagRunId` in Inline DAG Execution |
| 2026-02-21: GHSA-6v48-fcq6-ff23 (low): Path traversal in DAG creation allows arbitrary YAML file write outside DAGs directory |
Observability & Operations
adequateNo 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 |
5 of 5 deployed images carry no version, or `latest`
adequate5 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.
deploy/docker/compose.prod.yaml:6 — image without a version |
deploy/docker/compose.prod.yaml:13 — image without a version |
deploy/docker/compose.prod.yaml:26 — image without a version |
Readiness and liveness probes are identical in 4 of 5 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
charts/dagu/templates/coordinator-deployment.yaml — same probe endpoint twice |
charts/dagu/templates/scheduler-deployment.yaml — same probe endpoint twice |
charts/dagu/templates/worker-deployment.yaml — same probe endpoint twice |
1 of 6 deployments run a single replica
adequate1 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
deploy/k8s/server-deployment.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on dagucloud/dagu: 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.