getkirby/kirby: technical due diligence, read from its repository

The median source file here is 61 lines. 11 files exceed 1,000 lines, the largest being 1,763. 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.

The newest pre-release, 6.0.0-alpha.3, is not on the branch this survey read; the newest release on it is 5.6.0. The shipped product may differ from what this report describes. Survey the release branch too.

1 places read data with a deserialiser that executes what it reads (PHP `unserialize`). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.

1 of 48 locked dependencies match 1 published advisories in OSV. 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.

27 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.

Third-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.

LICENSE.md grants EULA: source available, not open source; use, copying and redistribution limited to what the agreement grants. 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.

The newest was published on 2026-09-16. 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 1 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 5.6.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 9 records name kirby with nothing tying them to this repository (CVE-2018-14519, CVE-2018-14520, CVE-2018-16623, …).