alfio-event/alf.io: technical due diligence, read from its repository

The median source file here is 44 lines. 19 files exceed 1,000 lines, the largest being 8,503. 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.

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

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

.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.

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

3 places read data with a deserialiser that executes what it reads (PHP `unserialize`, Ruby `Marshal.load`). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.

27 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.

The newest was published on 2026-09-18. 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 11 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 1.14.1. Answer lives in: the release you run, set against each fixed 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.