Read 2026-11-03
bulwarkmail/webmail: technical due diligence, read from its repository
What Borehole read in bulwarkmail/webmail's code and history at fbda1e3: 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 |
What the repository says
LICENSE: Relicensed: MIT → AGPL-3.0 (2026-03-16)CONTRIBUTING.md:31: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
stronglib/jmap/client.ts is 12,812 lines, 117× this codebase's median file
adequateThe median source file here is 109 lines. 34 files exceed 1,090 lines, the largest being 12,812. 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.
lib/jmap/client.ts:1 — 12,812 lines (117× median) |
stores/email-store.ts:1 — 8,740 lines (80× median) |
components/email/email-composer.tsx:1 — 6,313 lines (57× median) |
components/email/email-viewer.tsx:1 — 6,157 lines (56× median) |
components/mail/mail-app.tsx:1 — 5,866 lines (53× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (scripts/lite/smoke/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.
scripts/lite/smoke/playwright.config.ts:21 — test retry |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 2 cited: JWT, where fakes are usual |
The build runs third-party code it does not pin
adequate4 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; 4 steps pipe 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/docker-publish-lite.yml:50 — action pinned by tag |
.github/workflows/docker-publish-lite.yml:53 — action pinned by tag |
setup.sh:1210 — download piped into a shell |
1 of 3 Kubernetes workloads declare no resource limits
adequate1 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
deploy/kubernetes/overlays/config-in-git/config-from-files.yaml — workload with no limits |
15 places insert HTML from a variable without sanitising it
adequate15 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/(main)/layout.tsx:308 — HTML from a variable |
components/email/compose-format.ts:157 — HTML from a variable |
components/email/email-composer.tsx:4897 — HTML from a variable |
Relicensed: MIT → AGPL-3.0 (2026-03-16)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
14 advisories against this project in the last 24 months, 11 high or critical
adequateThe newest was published on 2026-10-23. 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: 212 records name webmail with nothing tying them to this repository (CVE-2000-0507, CVE-2000-1100, CVE-2001-0021, …).
| 2026-10-23: GHSA-r2r7-pvh6-mvj5 (moderate), fixed in 1.16.0: Mobile sign-in handoff sends the mailbox password to any app that claims the bulwarkmobile:// scheme |
| 2026-09-19: GHSA-cqqx-mjcf-mh55 (high), fixed in 1.10.0: WOPI editor access token accepted as a full session cookie via jmap_stalwart_ctx |
| 2026-09-19: GHSA-qvr9-m8cq-7wvg (moderate), fixed in 1.10.0: Session fixation via unauthenticated cross-site POST to /api/auth/session |
| 2026-09-19: GHSA-96cx-gx36-3g79 (high), fixed in 1.10.0: Arbitrary code execution in the app origin via /plugin-sandbox postMessage |
| 2026-09-19: GHSA-wxcm-j4jc-9fxq (high), fixed in 1.10.0: Unauthenticated settings access via credential-free identity cookie minting |
Observability & Operations
adequateNo 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 3,205 files for 10 structured logging libraries; 0 matched |
1 of 2 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.
deploy/kubernetes/base/bulwark.yaml:57 — 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 bulwarkmail/webmail: 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.