Read 2026-11-07
semaphoreio/semaphore: technical due diligence, read from its repository
What Borehole read in semaphoreio/semaphore's code and history at a5b3f7f: 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
- Releases are cut from another branch than the one surveyed
ee/LICENSE: Part of the code is under a separate licence: ee/
Architecture & Codebase — including AI provenance
strongfront/lib/internal_api/billing.pb.ex is 1,960 lines, 32× this codebase's median file
adequateThe median source file here is 61 lines. 45 files exceed 1,000 lines, the largest being 1,960. 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.
front/lib/internal_api/billing.pb.ex:1 — 1,960 lines (32× median) |
badge/lib/internal_api/plumber.pipeline.pb.ex:1 — 1,718 lines (28× median) |
notifications/lib/internal_api/plumber.pipeline.pb.ex:1 — 1,718 lines (28× median) |
guard/lib/guard/id/api.ex:1 — 1,684 lines (27× median) |
guard/lib/internal_api/plumber.pipeline.pb.ex:1 — 1,631 lines (26× median) |
Engineering Process & SDLC Maturity
adequate5% of recent commits change more than 2,000 lines
adequate42 of 774 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 42 commits over 2,000 lines |
Product & Engineering Maturity
strongNode.js 16 is past end of life
adequateThe code is pinned to Node.js 16 (end of life 2023-09-11). None of these receives security fixes any more; the first stopped on 2023-09-11. 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.
front/Dockerfile — Node.js 16, end of life 2023-09-11 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.6.0, is not on the branch this survey read; the newest pre-release on it is v1.2.0-rc.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.6.0 |
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. 4 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.
| private key block, where fakes are usual |
7 Dockerfiles run 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.
feature_provider/Dockerfile — runs as root |
helm-chart/Dockerfile — runs as root |
plumber/block/Dockerfile — runs as root |
plumber/definition_validator/Dockerfile — runs as root |
2 environment files are committed
adequatefront/env/.env.internal-apis, github_hooks/.env are 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.
front/env/.env.internal-apis — committed environment file |
github_hooks/.env — committed environment file |
3 outbound calls can wait forever
adequate3 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
bootstrapper/pkg/github/github.go:52 — outbound call without a timeout |
ee/velocity/pkg/collector/superjerry.go:177 — outbound call without a timeout |
ee/velocity/pkg/proc/summary/downloader.go:55 — outbound call without a timeout |
91 locked dependencies have published vulnerabilities, 4 high or critical in what ships
adequate91 of 1,206 locked dependencies match 202 published advisories in OSV, 90 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.
auth/mix.lock — grpc 0.11.5: GHSA-grp7-v8xh-rj7h (critical), fixed in 1.0.0 |
ee/gofer/mix.lock — grpc 0.5.0: GHSA-grp7-v8xh-rj7h (critical), fixed in 1.0.0 |
branch_hub/mix.lock — grpc 0.5.0-beta.1: GHSA-grp7-v8xh-rj7h (critical), fixed in 1.0.0 |
32 places insert HTML from a variable without sanitising it
adequate32 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
front/assets/js/deployments/components/basics.js:80 — HTML from a variable |
front/assets/js/deployments/components/credentials.js:145 — HTML from a variable |
front/assets/js/deployments/components/credentials.js:165 — HTML from a variable |
Part of the code is under a separate licence: ee/
adequateA directory named for a paid edition carries its own licence. That code is usually not open source even where the rest is; what the buyer may do with each part differs.
ee/LICENSE — licence: unrecognised |
Observability & Operations
adequateAn error reporter is installed but never initialised
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 |
Has a reporting host, telemetry.semaphore.io; its default could not be read
adequatebootstrapper/pkg/installation/installation.go names telemetry.semaphore.io as a place to report to, and no setting read here shows whether reporting is on as shipped. For a buyer running it inside their own product, ask whether copies report by default, what is sent, how often, and whether the buyer's customers were told.
bootstrapper/pkg/installation/installation.go:42 — names telemetry.semaphore.io |
36 of 36 deployed images carry no version, or `latest`
adequate36 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.
artifacthub/helm/values.yaml:1 — image without a version |
auth/helm/values.yaml:1 — image without a version |
badge/helm/values.yaml:2 — image without a version |
Readiness and liveness probes are identical in 9 of 40 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
auth/helm/templates/deployment.yaml — same probe endpoint twice |
badge/helm/templates/badges-dpl.yaml — same probe endpoint twice |
front/helm/templates/job-page.yaml — same probe endpoint twice |
8 of 80 deployments run a single replica
adequate8 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
artifacthub/helm/templates/minimal-deployment.yaml — replicas: 1 |
helm-chart/templates/database.yaml — replicas: 1 |
helm-chart/templates/rabbitmq.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on semaphoreio/semaphore: 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.