ray-project/ray: technical due diligence, read from its repository

The median source file here is 127 lines. 88 files exceed 1,270 lines, the largest being 8,940. 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.

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

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

python/ray/dashboard/client/.env.production.local 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.

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

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

17 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.

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

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.

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-07-01. 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 0.7.0. Answer lives in: the release you run, set against each fixed version. GHSA-q279-jhrf-cc6v (critical), GHSA-hhrp-gw25-jr43 (high), GHSA-q5fh-2hc8-f6rq (moderate) are fixed in the surveyed commit; which release carries them cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: 30 records name ray with nothing tying them to this repository (CVE-2002-2036, CVE-2004-0701, CVE-2006-4049, …).

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 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.