Read 2026-10-23
apioo/fusio: technical due diligence, read from its repository
What Borehole read in apioo/fusio's code and history at 0e5401c: 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 | not assessable |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: GPL-3.0 → AGPL-3.0 (2015-07-07) → Apache-2.0 (2023-07-01)
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate48% of commit subjects are exact repeats of another subject, and subject length varies by only 12.0 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.
| 294× 'update deps' |
| 258× 'update changelog' |
| 63× 'update readme' |
Engineering Process & SDLC Maturity
adequateChange lands on the trunk with no trace of review
adequateIn the last 24 months, 0 of 163 commits (0.0%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. Every common review workflow leaves at least one of those, so either review happens somewhere this history cannot see, or it is not happening. A buyer should establish which before relying on the review story they are told.
| 0 of 163 commits in the last 24 months carry review evidence; 0.5% across all 1,983 |
26% of commit subjects say nothing about the change
adequate519 of 1,978 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
| 519/1,978 low-content subjects (26.2%) |
| 'update' |
| 'update' |
| 'update' |
| 'add backend' |
Product & Engineering Maturity
not assessableEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.69 to 1.43 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.69, second half 1.43 (split 2020-05-08) |
Security & Reliability Posture
strong1 environment file is committed
adequate.env is 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.
.env — committed environment file |
Relicensed: GPL-3.0 → AGPL-3.0 (2015-07-07) → Apache-2.0 (2023-07-01)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-11. 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 2 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 7.2.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: its keyword search for 'fusio' is too broad to read whole (2,410 records).
| 2026-08-11: CVE-2026-72551 (high): A remote code execution vulnerability in Apioo Fusio 8.8.3 allows authenticated users with the Developer role to execute arbitrary OS commands by exploiting a P |
| 2026-08-11: CVE-2026-72598 (moderate): A server-side request forgery vulnerability in Apioo Fusio 8.8.3 allows authenticated consumer-role users to make the server issue HTTP requests to internal net |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on apioo/fusio: 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.