aquasecurity/trivy: technical due diligence, read from its repository

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

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

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

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

2 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.

2 of 470 locked dependencies match 3 published advisories in OSV, 1 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.

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 root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

1 of them is on CISA's known-exploited list: check first whether the release you run has the fix. The newest was published on 2026-10-02. 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 3 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 0.76.0. 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.