Read 2026-10-28
versity/versitygw: technical due diligence, read from its repository
What Borehole read in versity/versitygw's code and history at d217a7e: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequatebackend/posix/posix.go is 8,489 lines, 60× this codebase's median file
adequateThe median source file here is 141 lines. 9 files exceed 1,410 lines, the largest being 8,489. 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/posix/posix.go:1 — 8,489 lines (60× median) |
webui/web/js/api.js:1 — 2,918 lines (20× median) |
backend/azure/azure.go:1 — 2,838 lines (20× median) |
iamapi/storage/vault.go:1 — 2,142 lines (15× median) |
backend/s3proxy/s3.go:1 — 1,978 lines (14× median) |
2 base images float: no version, or `latest`
adequate2 of 2 `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:1 — base image without a version |
Dockerfile:24 — base image without a version |
Engineering Process & SDLC Maturity
strongAlmost 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: CI workflows. 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 1,022 tracked files |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate4 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 4 cited: AWS access key, where fakes are usual |
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.
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/docker.yml:18 — action pinned by tag |
.github/workflows/docker.yml:22 — action pinned by tag |
8 advisories against this project in the last 24 months, 4 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. None of them affects the surveyed version.
| 2026-10-22: GHSA-8m8m-xrwv-8mpq (low), fixed in 1.10.0: posix: object keys under .sgwtmp/ reach other clients' in-progress multipart upload staging |
| 2026-10-13: GHSA-7qcr-88c3-f9p7 (high), fixed in v1.9.0: Path traversal via unvalidated uploadId and batch-delete keys |
| 2026-10-13: GHSA-5gjv-3vhq-4chv (moderate), fixed in 1.9.0: DrainRequestBody does not cover Transfer-Encoding: chunked, so an unread aws-chunked tail can absorb another tenant's signed request |
| 2026-09-08: GHSA-c7wx-9pfv-whxh (moderate), fixed in 1.8.0: Object Lock COMPLIANCE mode: retain-until date can be shortened, defeating WORM protection |
| 2026-09-08: GHSA-7c8h-9q99-mm84 (low), fixed in 1.8.0: Non-constant-time signature comparisons |
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 994 files for 10 structured logging libraries; 0 matched |
The service logs with print: 59 calls against 0 logger calls
adequate59 `print` or `console.log` calls in the service's code, and 0 calls through a logger. Printed lines carry no level and no context, cannot be switched off, and are hard to find again in production.
auth/iam.go:247 — print used for logging |
auth/iam.go:274 — print used for logging |
auth/iam.go:279 — print used for logging |
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 |
4 of 4 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.
extra/dashboard/docker-compose-metrics.yml:3 — image without a version |
extra/dashboard/docker-compose-metrics.yml:16 — image without a version |
extra/dashboard/docker-compose-metrics.yml:32 — 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 versity/versitygw: 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.