Read 2026-10-04
zellij-org/zellij: technical due diligence, read from its repository
What Borehole read in zellij-org/zellij's code and history at 208a0da: 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 | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:20: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongzellij-server/src/tab/unit/tab_tests.rs is 17,918 lines, 81× this codebase's median file
adequateThe median source file here is 219 lines. 32 files exceed 2,190 lines, the largest being 17,918. 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.
zellij-server/src/tab/unit/tab_tests.rs:1 — 17,918 lines (81× median) |
zellij-server/src/tab/unit/tab_integration_tests.rs:1 — 16,842 lines (76× median) |
zellij-server/src/unit/screen_tests.rs:1 — 14,941 lines (68× median) |
zellij-server/src/screen.rs:1 — 13,700 lines (62× median) |
zellij-server/src/plugins/unit/plugin_tests.rs:1 — 13,654 lines (62× median) |
Engineering Process & SDLC Maturity
adequate7% of recent commits change more than 2,000 lines
adequate42 of 564 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.
| 42 commits over 2,000 lines |
Product & Engineering Maturity
adequate10% of bug fixes add or change a test
adequateOf 319 fixes in the last 24 months, 31 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.
| 31 of 319 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v0.45.1, is not on the branch this survey read; the newest release on it is v0.44.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.45.1 |
Security & Reliability Posture
strongThe 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. 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/e2e.yml:35 — action pinned by tag |
.github/workflows/e2e.yml:43 — action pinned by tag |
12 locked dependencies have published vulnerabilities
adequate12 of 536 locked dependencies match 13 published advisories in OSV. 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.
Cargo.lock — atty 0.2.14: GHSA-g98v-hv3f-hcfr (low) |
Cargo.lock — rand 0.8.5: GHSA-cq8v-f236-94qc (low), fixed in 0.8.6 |
Cargo.lock — rand 0.9.0: GHSA-cq8v-f236-94qc (low), fixed in 0.9.3 |
1 vendored component with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
zellij-utils/src/vendored/mod.rs — 1 tracked files, no licence file |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 500 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 500 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No 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 |
1 of 1 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.
docker-compose.yml:5 — 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 zellij-org/zellij: 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.