magento/magento2: technical due diligence, read from its repository

62% of commit subjects are exact repeats of another subject, and subject length varies by only 33.5 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. This was read from the most recent 50,000 commits (11 Aug 2020 to 22 Oct 2026) only; older history was not read.

The median source file here is 73 lines. 113 files exceed 1,000 lines, the largest being 18,842. 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, 2.4.10-alpha1, is not on the branch this survey read; the newest release on it is 2.4.9. The shipped product may differ from what this report describes. Survey the release branch too. This was read from the most recent 50,000 commits (11 Aug 2020 to 22 Oct 2026) only; older history was not read.

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

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.