Read 2026-10-23
apache/apisix: technical due diligence, read from its repository
What Borehole read in apache/apisix's code and history at cea64fb: 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 | 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
AGENTS.md:2: names Apache Software Foundation.gitmodules:1: 3 submodule(s) this survey does not read: t/toolkit, .github/actions/action-semantic-pull-request, .github/actions/autocorrect
Architecture & Codebase — including AI provenance
strongapisix/init.lua is 1,958 lines, 14× this codebase's median file
adequateThe median source file here is 138 lines. 4 files exceed 1,380 lines, the largest being 1,958. 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.
apisix/init.lua:1 — 1,958 lines (14× median) |
apisix/plugin.lua:1 — 1,634 lines (11× median) |
apisix/plugins/openid-connect.lua:1 — 1,531 lines (11× median) |
apisix/plugins/prometheus/exporter.lua:1 — 1,488 lines (10× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (t/node/websocket-proxy.spec.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.
t/node/websocket-proxy.spec.ts:348 — test retry |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 3.19.0, is not on the branch this survey read; the newest release on it is 3.9.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 3.19.0 |
Security & Reliability Posture
adequate110 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. 46 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: private key block, where fakes are usual |
1 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.
docker/debian-dev/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate4 steps pipe a download straight into a shell. 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/check-changelog.yml:29 — download piped into a shell |
29 advisories against this project in the last 24 months, 9 high or critical
adequateThe newest was published on 2026-10-01. 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 29 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 3.9.0. Answer lives in: the release you run, set against each fixed version.
| 2026-10-01: CVE-2026-78242 (moderate): Insertion of sensitive information into log file vulnerability in Apache APISIX. This vulnerability can cause the unmasked header value to be written to the |
| 2026-10-01: CVE-2026-82806 (moderate): Exposure of data element to wrong session vulnerability in Apache APISIX. This issue affects Apache APISIX: from 2.3.0 before 3.7.0. Under a supported aut |
| 2026-10-01: CVE-2026-94212 (moderate): Improper verification of cryptographic signature vulnerability in Apache APISIX. Any unauthenticated attacker could impersonate any user on every route prote |
| 2026-10-01: CVE-2026-94220 (low): Cross-Site request forgery (CSRF) vulnerability in feishu-auth and dingtalk-auth plugins in Apache APISIX. An attacker who can get a user to click a crafted |
| 2026-10-01: CVE-2026-94250 (high): Allocation of resources without limits or throttling vulnerability in batch-requests plugin in Apache APISIX. An unauthenticated caller can drive a gateway w |
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/docker-compose-master.yaml:51 — 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 apache/apisix: 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.