linuxserver/heimdall: technical due diligence, read from its repository

The median source file here is 35 lines. 2 files exceed 1,000 lines, the largest being 28,372. 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.

36 files were marked deprecated over two years ago and still are, the oldest since Feb 2018. 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. 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.

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 newest was published on 2026-10-08. 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 2 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.8.3. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 11 records name Heimdall with nothing tying them to this repository (CVE-2024-51358, CVE-2025-12486, CVE-2026-12357, …).

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.