kubeflow/kubeflow: technical due diligence, read from its repository

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

Matches for private key block were committed at some point across 2,526 commits examined. The files that held them are no longer in the working tree — but removal from a file is not removal from the history, and the history is what transfers with the asset. What matters is whether each was rotated after it was committed. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when. 2 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.

The newest was published on 2026-10-29. 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 7 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 1.1.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 6 records name kubeflow with nothing tying them to this repository (CVE-2023-6570, CVE-2023-6571, CVE-2024-8901, …).