countly/countly-server: technical due diligence, read from its repository

The median source file here is 99 lines. 78 files exceed 1,000 lines, the largest being 22,918. 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 suite is configured to retry failing tests (.github/scripts/merge-shepherd.test.js). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.

Deleted lines per line added rose from 0.42 to 0.78 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.

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

3 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 18 steps pipe a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.

4 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.

The newest was published on 2026-09-10. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version.

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.

3 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.