Read 2026-10-28
dograh-hq/dograh: technical due diligence, read from its repository
What Borehole read in dograh-hq/dograh's code and history at 82ef848: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
README.md:191: states a policy on AI-generated contributions.gitmodules:1: 1 submodule(s) this survey does not read: pipecat
Architecture & Codebase — including AI provenance
strongapi/services/configuration/registry.py is 2,599 lines, 21× this codebase's median file
adequateThe median source file here is 119 lines. 17 files exceed 1,190 lines, the largest being 2,599. 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.
api/services/configuration/registry.py:1 — 2,599 lines (21× median) |
ui/public/embed/dograh-widget.js:1 — 2,490 lines (20× median) |
api/services/workflow/pipecat_engine.py:1 — 2,489 lines (20× median) |
sdk/typescript/src/_generated_models.ts:1 — 2,188 lines (18× median) |
api/services/pipecat/service_factory.py:1 — 1,979 lines (16× median) |
Engineering Process & SDLC Maturity
adequate8% of recent commits change more than 2,000 lines
adequate63 of 774 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.
| 63 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate7 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/api-tests.yml:104 — action pinned by tag |
.github/workflows/build-api-image.yml:33 — action pinned by tag |
scripts/setup_requirements.sh:67 — download piped into a shell |
20 locked dependencies have published vulnerabilities, 24 high or critical in what ships
adequate20 of 721 locked dependencies match 81 published advisories in OSV, 46 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/package-lock.json — @sentry/nextjs 10.63.0: GHSA-mchm-gjx6-7h55 (critical), fixed in 10.75.2 |
ui/package-lock.json — dompurify 3.4.11: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
ui/package-lock.json — next 15.5.20: GHSA-2464-fhr4-w9xw (critical), fixed in 15.5.28 |
Observability & Operations
adequateReadiness and liveness probes are identical in 1 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.
deploy/helm/dograh/values.yaml — same probe endpoint twice |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on dograh-hq/dograh: 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.