clidey/whodb: technical due diligence, read from its repository

The median source file here is 143 lines. 10 files exceed 1,430 lines, the largest being 19,681. 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.

The suite is configured to retry failing tests (frontend/e2e/playwright.config.mjs). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.

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.

15 of 1,355 locked dependencies match 36 published advisories in OSV, 22 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. None of the high or critical ones is in what the product ships: only the build reaches them: a bundler, a code generator, a build plugin, or a lockfile in a tooling directory; they are development dependencies.

The root licence changed 1 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

The newest was published on 2026-10-21. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed 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.