Read 2026-11-03
parabolinc/parabol: technical due diligence, read from its repository
What Borehole read in parabolinc/parabol's code and history at 19db634: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: MIT → Apache-2.0 (2016-02-09) → AGPL-3.0 (2016-07-14)
Architecture & Codebase — including AI provenance
strongpackages/server/postgres/migrations/2025-01-08T00:27:52.203Z_init.ts is 11,589 lines, 275× this codebase's median file
adequateThe median source file here is 42 lines. 3 files exceed 1,000 lines, the largest being 11,589. 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.
packages/server/postgres/migrations/2025-01-08T00:27:52.203Z_init.ts:1 — 11,589 lines (275× median) |
packages/server/__evals__/pagesSearch/heavyCorpus/heavyCorpusData.ts:1 — 1,505 lines (35× median) |
packages/server/dataloader/customLoaderMakers.ts:1 — 1,350 lines (32× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate352 test files against 4,689 source files (7.5%). 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.
| 352 test files / 4,689 source files |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/integration-tests/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.
packages/integration-tests/playwright.config.ts:27 — test retry |
Product & Engineering Maturity
adequate86 direct dependencies in a single manifest
adequatepackages/server/package.json declares 86 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.
packages/server/package.json — 86 declared |
packages/client/package.json — 71 declared |
package.json — 63 declared |
packages/mattermost-plugin/package.json — 10 declared |
Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.76 to 1.09 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.76, second half 1.09 (split 2021-05-28) |
10% of bug fixes add or change a test
adequateOf 703 fixes in the last 24 months, 70 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.
| 70 of 703 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate13 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/assign_reviewers.yml:17 — action pinned by tag |
.github/workflows/build.yml:28 — action pinned by tag |
1 SQL statement built from strings
adequate1 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
packages/server/graphql/private/queries/helpers/authCount.ts:17 — SQL built from a string |
25 locked dependencies have published vulnerabilities, 31 high or critical in what ships
adequate25 of 2,054 locked dependencies match 83 published advisories in OSV, 41 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.
pnpm-lock.yaml — dompurify 3.4.16: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
pnpm-lock.yaml — tar 6.2.1: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
pnpm-lock.yaml — brace-expansion 1.1.12: GHSA-3jxr-9vmj-r5cp (high), fixed in 1.1.16 |
11 places insert HTML from a variable without sanitising it
adequate11 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.
packages/client/components/IntegratedTaskContent.tsx:113 — HTML from a variable |
packages/client/components/TimelineHistoryLockedCard.tsx:58 — HTML from a variable |
packages/client/components/TypeAheadLabel.tsx:25 — HTML from a variable |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
packages/mattermost-plugin/webpack.config.js:49 — source maps in a production build |
Relicensed: MIT → Apache-2.0 (2016-02-09) → AGPL-3.0 (2016-07-14)
adequateThe root licence changed 2 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.
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 4,938 files for 10 structured logging libraries; 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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on parabolinc/parabol: 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.