streamdal/plumber: technical due diligence, read from its repository

Deleted lines per line added rose from 0.48 to 1.29 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.

The code is pinned to Go 1.20 (end of life 2024-02-06). None of these receives security fixes any more; the first stopped on 2024-02-06. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.

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

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.

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.

5 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.