Read 2026-11-03
mai-with-u/maibot: technical due diligence, read from its repository
What Borehole read in mai-with-u/maibot's code and history at c642954: 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
README.md:190: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongsrc/config/official_configs.py is 6,216 lines, 41× this codebase's median file
adequateThe median source file here is 151 lines. 45 files exceed 1,510 lines, the largest being 6,216. 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/config/official_configs.py:1 — 6,216 lines (41× median) |
src/webui/routers/memory.py:1 — 5,590 lines (37× median) |
src/A_memorix/core/storage/metadata_store.py:1 — 4,598 lines (30× median) |
src/A_memorix/core/utils/web_import_manager.py:1 — 4,512 lines (29× median) |
dashboard/src/routes/config/bot/hooks/complexFieldHooks.tsx:1 — 3,496 lines (23× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (dashboard/src/lib/plugin-api/config.test.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.
dashboard/src/lib/plugin-api/config.test.ts:150 — test retry |
Product & Engineering Maturity
strongNo finding.
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
adequate9 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/a-memorix-tests.yml:23 — action pinned by tag |
.github/workflows/check-webui.yml:28 — action pinned by tag |
41 SQL statements built from strings
adequate41 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 18 of them a value, not a table or column name, goes into the string. Where any of those values comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
src/A_memorix/core/runtime/services/bundle_admin_service.py:496 — SQL built from a string |
src/A_memorix/core/runtime/services/delete_admin_service.py:877 — SQL built from a string |
src/A_memorix/core/runtime/services/delete_admin_service.py:1375 — SQL built from a string |
19 locked dependencies have published vulnerabilities, 6 high or critical in what ships
adequate19 of 1,216 locked dependencies match 56 published advisories in OSV, 22 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.
dashboard/package-lock.json — deepmerge-ts 7.1.5: GHSA-ggr8-5vv4-36mx (high), fixed in 8.0.0 |
dashboard/pnpm-lock.yaml — deepmerge-ts 7.1.6: GHSA-ggr8-5vv4-36mx (high), fixed in 8.0.0 |
dashboard/pnpm-lock.yaml — seroval 1.6.7: GHSA-7rv5-mrxv-xcr9 (high), fixed in 1.6.8 |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,839 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 1,839 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 |
3 of 3 deployed images carry no version, or `latest`
adequate3 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:63 — image without a version |
docker-compose.yml:68 — 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 mai-with-u/maibot: 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.