Read 2026-10-23
openflagr/flagr: technical due diligence, read from its repository
What Borehole read in openflagr/flagr's code and history at e026211: 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 | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateswagger_gen/restapi/embedded_spec.go is 5,337 lines, 52× this codebase's median file
adequateThe median source file here is 101 lines. 1 file exceed 1,010 lines, the largest being 5,337. 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.
swagger_gen/restapi/embedded_spec.go:1 — 5,337 lines (52× median) |
1 base image floats: no version, or `latest`
adequate1 of 3 `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:22 — base image without a version |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (browser/flagr-ui/playwright.config.mjs). 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.
browser/flagr-ui/playwright.config.mjs:14 — test retry |
Product & Engineering Maturity
strongNode.js 20 is past end of life
adequateThe code is pinned to Node.js 20 (end of life 2026-04-30). None of these receives security fixes any more; the first stopped on 2026-04-30. 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.
Dockerfile — Node.js 20, end of life 2026-04-30 |
Security & Reliability Posture
adequate1 credential-shaped string 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.
| JWT, where fakes are usual |
None 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 531 tracked files; 0 present |
The build runs third-party code it does not pin
adequate4 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/cd_docker.yml:18 — action pinned by tag |
.github/workflows/cd_docker.yml:20 — action pinned by tag |
3 locked dependencies have published vulnerabilities, 2 high or critical in what ships
adequate3 of 373 locked dependencies match 9 published advisories in OSV, 3 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.
browser/flagr-ui/package-lock.json — markdown-it 14.3.1: GHSA-gfr2-rv44-r23c (high), fixed in 14.3.3 |
browser/flagr-ui/package-lock.json — vite 8.0.16: GHSA-587h-7wmj-h5pm (high), fixed in 8.3.3; reached only by the build |
browser/flagr-ui/package-lock.json — katex 0.16.47: GHSA-238p-pmpm-9mq7 (low), fixed in 0.18.2 |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-01-07. 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-01-07: GHSA-rwp9-5g7q-73q3 (critical), fixed in 0.0.0-20251009103504-fe83dc87aa40: OpenFlagr contains an authentication bypass vulnerability in the HTTP middleware |
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 |
3 of 6 deployed images carry no version, or `latest`
adequate3 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.
docker-compose.kafka.yml:32 — image without a version |
docker-compose.kafka.yml:43 — image without a version |
docker-compose.kafka.yml:58 — 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 openflagr/flagr: 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.