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

The median source file here is 71 lines. 7 files exceed 1,000 lines, the largest being 4,951. 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.

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

The newest release, 7.1.9, is not on the branch this survey read; the newest release on it is 4.1.0. The shipped product may differ from what this report describes. Survey the release branch too.

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

6 of 2,028 locked dependencies match 8 published advisories in OSV, 3 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.

LICENSE grants SSPL-1.0 with additional terms: source available, not open source; offering it as a service obliges publishing the whole service stack. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.

The root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.

The newest was published on 2026-09-15. 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 10 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 4.1.0. Answer lives in: the release you run, set against each fixed version. GHSA-gqr6-r77p-c2pj (high) is fixed in the surveyed commit; which release carries it cannot be told from this history, which does not place the release users run. Answer lives in: the version you run.

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.