Read 2026-10-23
avo-hq/avo: technical due diligence, read from its repository
What Borehole read in avo-hq/avo's code and history at 875894f: 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
LICENSE.md: Relicensed: MIT → a commercial licence (2020-10-15)
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongRuby 3.1 is past end of life
adequateThe code is pinned to Ruby 3.1 (end of life 2025-03-26). None of these receives security fixes any more; the first stopped on 2025-03-26. 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.
docker/Dockerfile — Ruby 3.1, end of life 2025-03-26 |
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 2,132 tracked files; 0 present |
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.
docker/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; 1 step pipes 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/build-release-notes.yml:10 — action pinned by tag |
.github/workflows/create-release.yml:13 — action pinned by tag |
docker/Dockerfile:10 — download piped into a shell |
5 locked dependencies have published vulnerabilities, 5 high or critical
adequate5 of 998 locked dependencies match 13 published advisories in OSV, 5 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
Licence text does not match a standard licence
adequateLICENSE.md exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
LICENSE.md:1 — 10 lines, unrecognised |
Relicensed: MIT → a commercial licence (2020-10-15)
adequateThe root licence changed 1 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.
LICENSE.md — MIT from 2020-06-06 |
LICENSE.md — a commercial licence from 2020-10-15 |
8 advisories against this project in the last 24 months, 5 high or critical
adequateThe newest was published on 2026-10-22. 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 4 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 4.3.4. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: its keyword search for 'avo' is too broad to read whole (3,066 records).
| 2026-10-22: GHSA-x65r-p6hf-94hv (moderate), fixed in 3.33.2: Missing authorization on Avo association show endpoint exposes related records |
| 2026-10-22: GHSA-h7x6-9mqf-vgmx (high), fixed in 3.33.1: Global Avo.configuration.locale mutation via params[:set_locale] (process-wide state poisoning) |
| 2026-08-13: GHSA-cff8-4h3c-9r4q (high), fixed in 3.32.4: MediaLibraryController exposes every ActiveStorage::Blob to any authenticated Avo user (cross-resource IDOR) |
| 2026-08-10: GHSA-49qj-7hqj-6whp (high), fixed in 3.32.2: IDOR — Cross-tenant Active Storage Attachment Deletion in Avo |
| 2026-06-17: GHSA-8fq9-273g-6mrg (critical), fixed in 3.32.1: Avo: Missing Authorization in Avo Association Attach Endpoint Allows Unauthorized Relationship Manipulation and Privilege Escalation |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,360 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,360 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 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,360 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 avo-hq/avo: 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.