Read 2026-10-23
victoriametrics/victorialogs: technical due diligence, read from its repository
What Borehole read in victoriametrics/victorialogs's code and history at 42fc8a0: 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 |
Architecture & Codebase — including AI provenance
stronglib/logstorage/parser.go is 4,085 lines, 40× this codebase's median file
adequateThe median source file here is 100 lines. 13 files exceed 1,000 lines, the largest being 4,085. 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.
lib/logstorage/parser.go:1 — 4,085 lines (40× median) |
lib/logstorage/block_result.go:1 — 2,901 lines (29× median) |
lib/logstorage/storage_search.go:1 — 1,926 lines (19× median) |
app/vmui/packages/vmui/src/constants/emojis.ts:1 — 1,917 lines (19× median) |
app/vlselect/logsql/logsql.go:1 — 1,857 lines (18× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.40 to 0.97 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.40, second half 0.97 (split 2022-10-11) |
Go 1.24 is past end of life
adequateThe code is pinned to Go 1.24 (end of life 2026-02-10). None of these receives security fixes any more; the first stopped on 2026-02-10. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
deployment/docker/victorialogs/datadog-serverless/aws/Dockerfile — Go 1.24, end of life 2026-02-10 |
Security & Reliability Posture
adequate10 Dockerfiles run 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.
app/victoria-logs/multiarch/Dockerfile — runs as root |
app/vlagent/multiarch/Dockerfile — runs as root |
app/vlogscli/multiarch/Dockerfile — runs as root |
codespell/Dockerfile — runs as root |
1 environment file is committed
adequateapp/vmui/packages/vmui/.env.victorialogs is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
app/vmui/packages/vmui/.env.victorialogs — committed environment file |
6 locked dependencies have published vulnerabilities, 3 high or critical in what ships
adequate6 of 163 locked dependencies match 11 published advisories in OSV, 4 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.
app/vmui/packages/vmui/package-lock.json — nanoid 3.3.16: GHSA-2v37-7h3g-55p8 (high), fixed in 3.3.18 |
app/vmui/packages/vmui/package-lock.json — react-router 7.18.1: GHSA-qwww-vcr4-c8h2 (high), fixed in 7.18.2; the advisory applies only under a condition it states |
app/vmui/packages/vmui/package-lock.json — source-map-js 1.2.1: GHSA-68fv-2mgg-jv7q (high), fixed in 1.2.2 |
1 workload setting give a container the host
adequate1 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
deployment/docker/victorialogs/journald/compose-base.yml:7 — privileged or host namespace |
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 1,205 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 |
1 of 26 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.
deployment/docker/victorialogs/grafana-alloy/compose-base.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 victoriametrics/victorialogs: 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.