Read 2026-10-22
dagster-io/dagster: technical due diligence, read from its repository
What Borehole read in dagster-io/dagster's code and history at d21ac06: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate136 direct dependencies in a single manifest
adequatety/master/pyproject.toml declares 136 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.
ty/master/pyproject.toml — 136 declared |
js_modules/ui-core/package.json — 49 declared |
ty/airflow/pyproject.toml — 42 declared |
python_modules/dagster/pyproject.toml — 32 declared |
40 files still carry code deprecated more than two years ago
adequate40 files were marked deprecated over two years ago and still are, the oldest since Mar 2023. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
python_modules/dagster/dagster/_core/definitions/asset_selection.py — deprecated since Mar 2023 |
python_modules/dagster/dagster/_core/definitions/schedule_definition.py — deprecated since Mar 2023 |
python_modules/libraries/dagster-aws/dagster_aws/athena/resources.py — deprecated since Apr 2023 |
python_modules/libraries/dagster-aws/dagster_aws/redshift/resources.py — deprecated since Apr 2023 |
python_modules/dagster/dagster/_core/definitions/definitions_class.py — deprecated since Apr 2023 |
Security & Reliability Posture
adequate8 Dockerfiles run 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.
The build runs third-party code it does not pin
adequate2 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; 1 step pipes a download straight into a shell. 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/build-docs.yml:95 — action pinned by tag |
.github/workflows/check-docs.yml:18 — action pinned by tag |
.buildkite/dagster-buildkite/dagster_buildkite/steps/dagster.py:138 — download piped into a shell |
73 locked dependencies have published vulnerabilities, 40 high or critical in what ships
adequate73 of 3,114 locked dependencies match 149 published advisories in OSV, 88 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
ty/airflow/uv.lock — apache-airflow 2.11.2: GHSA-2943-9672-r45w (critical), fixed in 3.3.0 |
python_modules/dagster-cloud/uv.lock — certifi 2025.1.31: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
helm/dagster/schema/uv.lock — certifi 2026.4.22: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
3 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-04-17. 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 1 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 14.2.0. Answer lives in: the release you run, set against each fixed version.
| 2026-04-17: GHSA-mjw2-v2hm-wj34 (high), fixed in 0.29.1: Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations |
| 2025-07-22: GHSA-h7x8-jv97-fvvm (moderate), fixed in 1.10.16: Dagster Local File Inclusion vulnerability |
| 2025-07-07: GHSA-q93c-p2mw-p23f (moderate), fixed in 1.5.11: Dagster vulnerable to Path Traversal attack through its /logs endpoint |
Observability & Operations
adequateOne 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 |
An error reporter is installed but never initialised
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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on dagster-io/dagster: 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.