Read 2026-10-23
tinyauthapp/tinyauth: technical due diligence, read from its repository
What Borehole read in tinyauthapp/tinyauth's code and history at 54d7dfe: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: GPL-3.0 → AGPL-3.0 (2026-05-21)AI_POLICY.md:1: states a policy on AI-generated contributionsREADME.md:13: names OpenSSF
Architecture & Codebase — including AI provenance
stronginternal/service/oidc_service.go is 1,120 lines, 18× this codebase's median file
adequateThe median source file here is 61 lines. 1 file exceed 1,000 lines, the largest being 1,120. 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.
internal/service/oidc_service.go:1 — 1,120 lines (18× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (e2e/playwright.config.ts). 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.
e2e/playwright.config.ts:7 — test retry |
Product & Engineering Maturity
adequate18% of bug fixes add or change a test
adequateOf 193 fixes in the last 24 months, 35 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 35 of 193 |
Security & Reliability Posture
adequate1 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 |
8 locked dependencies have published vulnerabilities, 4 high or critical in what ships
adequate8 of 593 locked dependencies match 16 published advisories in OSV, 8 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.
go.mod — github.com/docker/docker v28.5.2+incompatible: GO-2026-4887 (high) |
frontend/pnpm-lock.yaml — follow-redirects 1.16.0: GHSA-8r9p-f939-6h3c (high), fixed in 1.16.1 |
frontend/pnpm-lock.yaml — zod 4.6.5: GHSA-mrhx-c7xc-m3w5 (high), fixed in 4.6.6 |
Relicensed: GPL-3.0 → AGPL-3.0 (2026-05-21)
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.
9 advisories against this project in the last 24 months, 6 high or critical
adequateThe newest was published on 2026-09-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. Whether 1 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 5.2.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 3 records name tinyauth with nothing tying them to this repository (CVE-2026-32245, CVE-2026-32246, CVE-2026-33544).
| 2026-09-07: GHSA-vx8c-f5hh-c8pf (critical), fixed in >= 5.2.0: Nginx authentication bypass via spoofed X-Original-URL header |
| 2026-07-30: GHSA-r27r-rr9v-vv37 (high), fixed in >= v5.1.3: Authentication bypass via improper path matching |
| 2026-07-15: GHSA-328g-jx67-v94g (high), fixed in 1.0.1-0.20260720133915-80bc87188ec3: Tinyauth: forward-auth per-app ACL is matched case-sensitively against the (case-insensitive) hostname, letting an authenticated user reach apps they are not on |
| 2026-07-15: GHSA-456h-ww26-f758 (moderate), fixed in 1.0.1-0.20260714134959-c22925c2fba9: Tinyauth: User enumeration attack by timing oracle |
| 2026-07-15: GO-2026-6564 (moderate), fixed in 1.0.1-0.20260715123057-dade1e2c8f27: Tinyauth: Unauthenticated login attempts can trigger global login lockdown denial of service in github.com/tinyauthapp/tinyauth |
Observability & Operations
adequateOne 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 |
1 of 3 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.
docker-compose.example.yml:11 — 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 tinyauthapp/tinyauth: 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.