Read 2026-10-23
apache/shenyu: technical due diligence, read from its repository
What Borehole read in apache/shenyu's code and history at 34f2ed0: 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
Architecture & Codebase — including AI provenance
strongdb/init/oracle/schema.sql is 3,491 lines, 37× this codebase's median file
adequateThe median source file here is 93 lines. 9 files exceed 1,000 lines, the largest being 3,491. 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.
db/init/oracle/schema.sql:1 — 3,491 lines (37× median) |
db/init/pg/create-table.sql:1 — 2,950 lines (31× median) |
db/init/mysql/schema.sql:1 — 2,487 lines (26× median) |
shenyu-common/src/main/java/org/apache/shenyu/common/config/ShenyuConfig.java:1 — 2,280 lines (24× median) |
shenyu-admin/src/main/resources/sql-script/h2/schema.sql:1 — 1,599 lines (17× median) |
Engineering Process & SDLC Maturity
strongAlmost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 4,815 tracked files |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v2.7.1, is not on the branch this survey read; the newest release on it is 1.0.5. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.7.1 |
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 |
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.
shenyu-integrated-test/shenyu-integrated-test-k8s-gateway-api-http/Dockerfile — runs as root |
46 of 47 Kubernetes workloads declare no resource limits
adequate46 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
shenyu-e2e/shenyu-e2e-case/k8s/shenyu-etcd.yml — workload with no limits |
shenyu-e2e/shenyu-e2e-case/k8s/shenyu-mysql.yml — workload with no limits |
shenyu-e2e/shenyu-e2e-case/k8s/shenyu-nacos.yml — workload with no limits |
2 workload settings give a container the host
adequate2 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
shenyu-e2e/shenyu-e2e-case/compose/sync/shenyu-nacos.yml:68 — privileged or host namespace |
shenyu-e2e/shenyu-e2e-case/k8s/shenyu-nacos.yml:50 — privileged or host namespace |
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 4,386 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 |
20 of 29 deployed images carry no version, or `latest`
adequate20 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.
shenyu-e2e/shenyu-e2e-case/k8s/shenyu-zookeeper.yml:35 — image without a version |
shenyu-examples/shenyu-examples-http/k8s/shenyu-deployment.yml:38 — image without a version |
shenyu-examples/shenyu-examples-http/k8s/shenyu-deployment.yml:75 — image without a version |
Readiness and liveness probes are identical in 15 of 18 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.
shenyu-e2e/shenyu-e2e-case/k8s/sync/shenyu-admin-etcd.yml — same probe endpoint twice |
shenyu-e2e/shenyu-e2e-case/k8s/sync/shenyu-admin-http.yml — same probe endpoint twice |
shenyu-e2e/shenyu-e2e-case/k8s/sync/shenyu-admin-nacos.yml — same probe endpoint twice |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on apache/shenyu: 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.