Read 2026-10-04
docusealco/docuseal: technical due diligence, read from its repository
What Borehole read in docusealco/docuseal's code and history at 44dcc7f: 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 | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongapp/javascript/template_builder/builder.vue is 4,031 lines, 93× this codebase's median file
adequateThe median source file here is 43 lines. 11 files exceed 1,000 lines, the largest being 4,031. 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.
app/javascript/template_builder/builder.vue:1 — 4,031 lines (93× median) |
lib/pdfium.rb:1 — 2,359 lines (54× median) |
app/javascript/submission_form/form.vue:1 — 1,843 lines (42× median) |
app/javascript/template_builder/i18n.js:1 — 1,773 lines (41× median) |
app/javascript/submission_form/i18n.js:1 — 1,670 lines (38× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate63 test files against 633 source files (10.0%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 63 test files / 633 source files |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 1,129 tracked files |
Product & Engineering Maturity
adequate4% of bug fixes add or change a test
adequateOf 500 fixes in the last 24 months, 18 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 18 of 500 |
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 |
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/ci.yml:13 — action pinned by tag |
.github/workflows/docker.yml:21 — action pinned by tag |
63 locked dependencies have published vulnerabilities, 79 high or critical
adequate63 of 1,229 locked dependencies match 155 published advisories in OSV, 79 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.
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.
app/javascript/elements/dashboard_dropzone.js:125 — HTML from a variable |
app/javascript/elements/dashboard_dropzone.js:161 — HTML from a variable |
app/javascript/elements/html_editor.js:525 — HTML from a variable |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2024-12-04. 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 3.3.0. Answer lives in: the release you run, set against each fixed version.
| 2024-12-04: CVE-2024-52277 (high): User Interface (UI) Misrepresentation of Critical Information vulnerability in DocuSeal allows Content Spoofing.Displayed version does not show the layer flatte |
Observability & Operations
strong2 of 3 deployed images carry no version, or `latest`
adequate2 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:6 — image without a version |
docker-compose.yml:30 — 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 docusealco/docuseal: 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.