Read 2026-10-04
pocketbase/pocketbase: technical due diligence, read from its repository
What Borehole read in pocketbase/pocketbase's code and history at 5cec579: 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 | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:5: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongui/src/utils.js is 1,851 lines, 12× this codebase's median file
adequateThe median source file here is 154 lines. 4 files exceed 1,540 lines, the largest being 1,851. 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.
ui/src/utils.js:1 — 1,851 lines (12× median) |
core/base.go:1 — 1,661 lines (10× median) |
core/record_model.go:1 — 1,647 lines (10× median) |
core/app.go:1 — 1,582 lines (10× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 45 of 1,113 commits (4.0%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. That is low but not absent. Review may happen in a workflow this history does not record; a buyer should ask how change is approved before it ships.
| 45 of 1,113 commits in the last 24 months carry review evidence; 7.6% across all 2,538 |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate339 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. 15 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| 5 cited: JWT, where fakes are usual |
1 environment file is committed
adequateui/.env 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.
ui/.env — committed environment file |
1 locked dependency has published vulnerabilities
adequate1 of 43 locked dependencies match 1 published advisories in OSV. 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.
go.mod — github.com/disintegration/imaging v1.6.2: GHSA-q7pp-wcgr-pffx (low) |
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-07-16. 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. The record is incomplete: NVD: 1 record names pocketbase with nothing tying it to this repository (CVE-2024-31218).
| 2026-07-16: GHSA-84vh-m24q-wjjx (high), fixed in 0.22.48: Pocketbase: Unhandled panic in worker goroutines |
| 2026-04-27: GHSA-pq7p-mc74-g65w (moderate), fixed in 0.22.42: PocketBase vulnerable to account pre-hijacking via OAuth2 unverfied->verified autolinking upgrade |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 691 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 691 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 |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 pocketbase/pocketbase: 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.