Read 2026-11-03
permitio/opal: technical due diligence, read from its repository
What Borehole read in permitio/opal's code and history at 83d17ac: 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 |
What the repository says
LICENSE: Relicensed: GPL-3.0 → Apache-2.0 (2021-03-30).gitmodules:1: 1 submodule(s) this survey does not read: cedar-agent
Architecture & Codebase — including AI provenance
adequatepackages/opal-server/opal_server/git_fetcher.py is 3,228 lines, 31× this codebase's median file
adequateThe median source file here is 102 lines. 2 files exceed 1,020 lines, the largest being 3,228. 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.
packages/opal-server/opal_server/git_fetcher.py:1 — 3,228 lines (31× median) |
packages/opal-client/opal_client/policy_store/opa_client.py:1 — 1,046 lines (10× median) |
2 base images float: no version, or `latest`
adequate2 of 17 `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.
docker/Dockerfile:111 — base image without a version |
docker/Dockerfile:167 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 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.
| 2 cited: private key block, where fakes are usual |
The build runs third-party code it does not pin
adequate6 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/on_release.yml:54 — action pinned by tag |
.github/workflows/on_release.yml:57 — action pinned by tag |
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 402 files for 10 structured logging libraries; 0 matched |
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 |
9 of 17 deployed images carry no version, or `latest`
adequate9 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/docker-compose-with-statistics.yml:18 — image without a version |
docker/docker-compose-with-statistics.yml:47 — image without a version |
docker/docker-compose-api-policy-source-example.yml:72 — 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 permitio/opal: 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.