conductor-oss/conductor: technical due diligence, read from its repository

The median source file here is 86 lines. 29 files exceed 1,000 lines, the largest being 3,849. 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 (ui-next/playwright.config.ts). 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.

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

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

ui-next/.env, ui/.env are 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.

12 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; 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.

The newest was published on 2026-06-30. 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 1 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 3.32.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 13 records name conductor with nothing tying them to this repository (CVE-2012-6118, CVE-2015-0652, CVE-2015-0653, …).

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.

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