Read 2026-10-23
sysadminsmedia/homebox: technical due diligence, read from its repository
What Borehole read in sysadminsmedia/homebox's code and history at 1fd2882: 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 | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:17: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
adequateCommit messages are templated rather than written
adequate36% of commit subjects are exact repeats of another subject, and subject length varies by only 17.7 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 164× 'Translated using Weblate (Japanese)' |
| 80× 'Translated using Weblate (Hungarian)' |
| 76× 'Translated using Weblate (Spanish)' |
backend/internal/data/repo/repo_entities.go is 3,226 lines, 65× this codebase's median file
adequateThe median source file here is 49 lines. 4 files exceed 1,000 lines, the largest being 3,226. 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.
backend/internal/data/repo/repo_entities.go:1 — 3,226 lines (65× median) |
backend/internal/core/services/service_exports.go:1 — 1,580 lines (32× median) |
backend/internal/data/repo/repo_item_attachments.go:1 — 1,105 lines (22× median) |
frontend/pages/item/[id]/index/edit.vue:1 — 1,055 lines (21× median) |
1 base image floats: no version, or `latest`
adequate1 of 5 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
Dockerfile:69 — base image without a version |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (frontend/test/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.
frontend/test/playwright.config.ts:8 — test retry |
Product & Engineering Maturity
adequate18% of bug fixes add or change a test
adequateOf 299 fixes in the last 24 months, 53 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.
| 53 of 299 |
Fixes are 62% of recent work, up from 22%
adequateIn the last two quarters 62% of commits were fixes, against 22% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 65%, 58%, 41%, 29%, 13%, 13%, 15%, 22% |
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
adequate2 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; 5 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/upgrade-test.yaml:32 — action pinned by tag |
.github/workflows/upgrade-test.yaml:40 — action pinned by tag |
.gitlab-ci.yml:305 — download piped into a shell |
3 SQL statements built from strings
adequate3 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
backend/internal/core/services/service_exports.go:507 — SQL built from a string |
backend/internal/core/services/service_exports.go:651 — SQL built from a string |
backend/internal/core/services/service_exports.go:1559 — SQL built from a string |
22 locked dependencies have published vulnerabilities, 22 high or critical in what ships
adequate22 of 1,628 locked dependencies match 61 published advisories in OSV, 28 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.
frontend/pnpm-lock.yaml — @simple-git/argv-parser 1.1.1: GHSA-v5rq-49vh-5v5c (critical), fixed in 2.0.1 |
frontend/pnpm-lock.yaml — dompurify 3.4.16: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
frontend/pnpm-lock.yaml — protobufjs 8.0.0: GHSA-xq3m-2v4x-88gg (critical), fixed in 8.0.1 |
25 advisories against this project in the last 24 months, 7 high or critical
adequateThe newest was published on 2026-10-17. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.27.1. Answer lives in: the release you run, set against each fixed version.
| 2026-10-17: GHSA-mw9p-fhpj-jf82 (moderate), fixed in 0.27.0: Invitation usage limit is raceable, oversubscribing a group beyond the owner-granted quota in Homebox |
| 2026-10-17: GHSA-h7wm-wjr6-cfxh (moderate), fixed in 0.27.0: CSV formula injection in entities export and bill-of-materials export |
| 2026-10-17: GHSA-mgw9-qw3h-224m (moderate), fixed in 0.27.0: Session bearer tokens accepted from query strings and emitted by the frontend on attachment URLs — credential leakage to logs/history |
| 2026-10-17: GHSA-58m4-m8xj-v3j2 (high), fixed in 0.27.0: Unauthenticated /api/v1/users/register lacks rate limiting while Argon2id runs per request (default-enabled) — resource exhaustion DoS |
| 2026-10-17: GHSA-754m-5j7m-8wfv (moderate), fixed in 0.27.0: Unauthenticated X-Forwarded-Host injection into /swagger/doc.json lets an attacker control the host of the served OpenAPI spec (host-header injection / cache po |
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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on sysadminsmedia/homebox: 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.