halo-dev/halo: technical due diligence, read from its repository

The median source file here is 59 lines. 8 files exceed 1,000 lines, the largest being 1,497. 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 release, v2.27.1, is not on the branch this survey read; the newest release on it is v2.27.0. The shipped product may differ from what this report describes. Survey the release branch too.

ui/.env.production 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.

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

5 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.

The newest was published on 2026-10-21. 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 13 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 2.27.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 18 records name halo with nothing tying them to this repository (CVE-2004-1539, CVE-2004-1667, CVE-2005-1741, …).

Nothing 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.

12 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.