feast-dev/feast: technical due diligence, read from its repository

The median source file here is 102 lines. 38 files exceed 1,020 lines, the largest being 5,213. 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 code is pinned to Node.js 17 (end of life 2022-06-01); Python 3.9 (end of life 2025-10-31). None of these receives security fixes any more; the first stopped on 2022-06-01. 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.

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

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

7 places in product code build SQL by formatting or joining strings rather than passing parameters. 2 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.

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

2 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.

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 newest was published on 2026-09-16. 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.67.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 8 records name feast with nothing tying them to this repository (CVE-2024-11602, CVE-2026-18941, CVE-2026-18942, …).

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.