Read 2026-11-03
evolution-foundation/evolution-api: technical due diligence, read from its repository
What Borehole read in evolution-foundation/evolution-api's code and history at fa09d37: 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 | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE:1: The licence is Apache-2.0 with a commercial-licence condition: source available, not open sourceLICENSE: Relicensed: GPL-3.0 → Apache-2.0 with a commercial-licence condition (2024-10-04).gitmodules:1: 1 submodule(s) this survey does not read: evolution-manager-v2
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate37% of commit subjects are exact repeats of another subject, and subject length varies by only 29.1 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 52× 'changelog' |
| 12× 'wip' |
| 12× 'git actions v2' |
src/api/integrations/channel/whatsapp/whatsapp.baileys.service.ts is 5,123 lines, 121× this codebase's median file
adequateThe median source file here is 42 lines. 4 files exceed 1,000 lines, the largest being 5,123. 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.
src/api/integrations/channel/whatsapp/whatsapp.baileys.service.ts:1 — 5,123 lines (121× median) |
src/api/integrations/chatbot/chatwoot/services/chatwoot.service.ts:1 — 2,715 lines (64× median) |
src/api/integrations/channel/meta/whatsapp.business.service.ts:1 — 1,772 lines (42× median) |
src/api/integrations/chatbot/typebot/services/typebot.service.ts:1 — 1,023 lines (24× median) |
Engineering Process & SDLC Maturity
adequateTests are absent or token
adequate0 test files against 269 source files (0.0%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 0 test files / 269 source files |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest pre-release, 2.4.0-rc2, is not on the branch this survey read; the newest release on it is 2.3.7. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 2.4.0-rc2 |
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 |
The build runs third-party code it does not pin
adequate5 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; 1 step pipes 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/publish_docker_image.yml:23 — action pinned by tag |
.github/workflows/publish_docker_image.yml:29 — action pinned by tag |
local_install.sh:96 — download piped into a shell |
38 locked dependencies have published vulnerabilities, 64 high or critical in what ships
adequate38 of 762 locked dependencies match 155 published advisories in OSV, 69 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.
package-lock.json — fast-xml-parser 4.5.3: GHSA-m7jm-9gc2-mpf2 (critical), fixed in 4.5.4 |
package-lock.json — fast-xml-parser 5.2.5: GHSA-m7jm-9gc2-mpf2 (critical), fixed in 5.3.5 |
package-lock.json — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
The licence is Apache-2.0 with a commercial-licence condition: source available, not open source
adequateLICENSE grants Apache-2.0 with a commercial-licence condition: source available, not open source; some uses need a commercial licence from the licensor. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE:1 — 208 lines, Apache-2.0 AND LicenseRef-Terms-CommercialLicence |
Relicensed: GPL-3.0 → Apache-2.0 with a commercial-licence condition (2024-10-04)
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.
Observability & Operations
strong5 of 7 deployed images carry no version, or `latest`
adequate5 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/minio/docker-compose.yaml:6 — image without a version |
Docker/postgres/docker-compose.yaml:21 — image without a version |
docker-compose.yaml:6 — 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 evolution-foundation/evolution-api: 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.