Read 2026-10-23
getmaxun/maxun: technical due diligence, read from its repository
What Borehole read in getmaxun/maxun's code and history at 8f2ab6b: 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 |
What the repository says
CONTRIBUTING.md:48: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongsrc/helpers/clientSelectorGenerator.ts is 4,499 lines, 35× this codebase's median file
adequateThe median source file here is 127 lines. 16 files exceed 1,270 lines, the largest being 4,499. 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.
src/helpers/clientSelectorGenerator.ts:1 — 4,499 lines (35× median) |
maxun-core/src/interpret.ts:1 — 3,310 lines (26× median) |
server/src/workflow-management/selector.ts:1 — 3,092 lines (24× median) |
server/src/sdk/workflowEnricher.ts:1 — 3,030 lines (23× median) |
server/src/sdk/browserSide/pageAnalyzer.js:1 — 2,811 lines (22× median) |
55 errors caught and discarded in product code
adequate55 places catch an error and do nothing with it, across 14 files (0.6 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
maxun-core/src/interpret.ts:597 — error caught and discarded |
maxun-core/src/interpret.ts:612 — error caught and discarded |
maxun-core/src/interpret.ts:681 — error caught and discarded |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate1 test files against 234 source files (0.4%). 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.
| 1 test files / 234 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: contribution guidance. 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 294 tracked files |
Product & Engineering Maturity
adequate89 direct dependencies in a single manifest
adequatepackage.json declares 89 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.
package.json — 89 declared |
maxun-core/package.json — 5 declared |
browser/package.json — 3 declared |
1% of bug fixes add or change a test
adequateOf 870 fixes in the last 24 months, 13 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.
| 13 of 870 |
Fixes are 50% of recent work, up from 23%
adequateIn the last two quarters 50% of commits were fixes, against 23% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 46%, 55%, 50%, 33%, 27%, 13%, 5%, 11% |
2 jobs are each done by more than one library
adequateWithin a single package: CSS-in-JS: emotion, styled-components; HTTP clients: axios, node-fetch. Each duplicate is bundle size, two ways of doing the same thing in one codebase, and two upgrade paths to maintain. It is usually the residue of a migration that stopped halfway.
package.json — several libraries per job |
Security & Reliability Posture
adequate122 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
browser/package.json:13 — ^4.3.6 |
browser/package.json:14 — ^2.11.2 |
browser/package.json:17 — ^22.7.9 |
browser/package.json:18 — ^5.0.0 |
browser/package.json:19 — ^10.9.2 |
1 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.
browser/Dockerfile — runs as root |
8 places insert HTML from a variable without sanitising it
adequate8 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.
server/src/workflow-management/selector.ts:297 — HTML from a variable |
server/src/workflow-management/selector.ts:298 — HTML from a variable |
server/src/workflow-management/selector.ts:600 — HTML from a variable |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-06-25. 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: 2 records name maxun with nothing tying them to this repository (CVE-2025-15105, CVE-2025-15106).
| 2026-06-25: CVE-2026-56767 (high): Maxun before 0.0.42 contains a cross-tenant insecure direct object reference vulnerability in storage and webhook API handlers that allows authenticated users t |
Observability & Operations
strongNo 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 |
4 of 5 deployed images carry no version, or `latest`
adequate4 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:20 — image without a version |
docker-compose.yml:36 — image without a version |
docker-compose.yml:67 — 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 getmaxun/maxun: 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.