onlyoffice/communityserver: technical due diligence, read from its repository

61% of commit subjects are exact repeats of another subject, and subject length varies by only 8.9 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 71 lines. 156 files exceed 1,000 lines, the largest being 21,614. 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.

32 files were marked deprecated over two years ago and still are, the oldest since Nov 2020. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.

4 places in product code build SQL by formatting or joining strings rather than passing parameters. 3 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.

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.

The root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

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.