Read 2026-11-03
argoproj/argo-rollouts: technical due diligence, read from its repository
What Borehole read in argoproj/argo-rollouts's code and history at 3fe7061: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
README.md:7: names OpenSSF
Architecture & Codebase — including AI provenance
adequatepkg/apis/rollouts/v1alpha1/openapi_generated.go is 6,192 lines, 43× this codebase's median file
adequateThe median source file here is 142 lines. 3 files exceed 1,420 lines, the largest being 6,192. 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.
pkg/apis/rollouts/v1alpha1/openapi_generated.go:1 — 6,192 lines (43× median) |
rollout/trafficrouting/istio/istio.go:1 — 1,683 lines (11× median) |
pkg/apiclient/rollout/rollout.pb.gw.go:1 — 1,509 lines (10× median) |
2 base images float: no version, or `latest`
adequate2 of 5 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
Dockerfile:73 — base image without a version |
Dockerfile:88 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v1.10.1, is not on the branch this survey read; the newest release on it is v1.2.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.10.1 |
Security & Reliability Posture
adequate1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key. 1 other match 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.
| Slack token, where fakes are usual |
The build runs third-party code it does not pin
adequate6 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.
.github/workflows/changelog.yml:26 — action pinned by tag |
.github/workflows/docker-publish.yml:41 — action pinned by tag |
.github/workflows/testing.yaml:157 — download piped into a shell |
3 of 5 Kubernetes workloads declare no resource limits
adequate3 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.
manifests/dashboard-install.yaml — workload with no limits |
manifests/dashboard-install/dashboard-deployment.yaml — workload with no limits |
manifests/namespace-install/add-namespaced-flag.yaml — workload with no limits |
61 locked dependencies have published vulnerabilities, 3 high or critical in what ships
adequate61 of 1,929 locked dependencies match 145 published advisories in OSV, 78 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.
ui/pnpm-lock.yaml — eventsource 1.1.0: GHSA-6h5x-7c5m-7cr7 (critical), fixed in 1.1.1; a development dependency |
ui/pnpm-lock.yaml — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8; a development dependency |
ui/pnpm-lock.yaml — tar 6.1.0: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19; a development dependency |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
ui/src/app/webpack.common.js:22 — source maps in a production build |
ui/src/app/webpack.prod.js:8 — source maps in a production build |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-28. 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 1.2.0. Answer lives in: the release you run, set against each fixed version.
| 2026-08-28: CVE-2026-82277 (critical): Argo Rollouts dashboard through 1.10.0 binds to all interfaces and exposes mutating Rollout operations without authentication, authorization, or CSRF protection |
Observability & Operations
strongNo error reporter is wired in
adequateNothing 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.
| no error reporter initialised |
3 of 3 deployed images carry no version, or `latest`
adequate3 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.
manifests/namespace-install.yaml:394 — image without a version |
manifests/dashboard-install.yaml:134 — image without a version |
manifests/dashboard-install/dashboard-deployment.yaml:22 — image without a version |
4 of 5 deployments run a single replica
adequate4 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.
manifests/base/argo-rollouts-deployment.yaml — replicas: 1 |
manifests/dashboard-install.yaml — replicas: 1 |
manifests/dashboard-install/dashboard-deployment.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on argoproj/argo-rollouts: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.