walkor/workerman: technical due diligence, read from its repository

36% of commit subjects are exact repeats of another subject, and subject length varies by only 19.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.

The median source file here is 182 lines. 1 file exceed 1,820 lines, the largest being 2,877. 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.

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

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