Borehole · Project · free tier
fluxcd/flagger
Free reading: not for reliance
c781cdc · 3,178 commits · 798 files
Read 2026-10-23

fluxcd/flagger: technical due diligence, read from its repository

What Borehole read in fluxcd/flagger's code and history at c781cdc: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturityadequate
Security & Reliability Posturestrong
Observability & Operationsstrong
Fit with the Acquirernot assessable

What the repository says

  • CONTRIBUTING.md:31: names CNCF
  • README.md:19: names Cloud Native Computing Foundation

Architecture & Codebase — including AI provenance

strong
01.6

pkg/apis/gatewayapi/v1/httproute_types.go is 1,850 lines, 26× this codebase's median file

adequate

The median source file here is 71 lines. 5 files exceed 1,000 lines, the largest being 1,850. 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.

Evidence
pkg/apis/gatewayapi/v1/httproute_types.go:1 — 1,850 lines (26× median)
pkg/controller/scheduler.go:1 — 1,089 lines (15× median)
pkg/apis/gatewayapi/v1/shared_types.go:1 — 1,031 lines (14× median)
pkg/apis/projectcontour/v1/httpproxy.go:1 — 1,028 lines (14× median)
pkg/apis/gatewayapi/v1beta1/httproute_types.go:1 — 1,024 lines (14× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

adequate
04.2

645 unresolved debt markers, 5.9 per thousand lines

adequate

The codebase carries 645 TODO, FIXME, HACK or XXX markers across 109,399 lines. These are the team's own notes about work they knew was unfinished. A high density is not automatically bad — it can mean an honest team — but every one of them is a decision deferred, and after an acquisition they are deferred onto someone who was not in the room.

Evidence
cmd/flagger/main.go:407 — _, err := flaggerClient.FlaggerV1beta1().Canaries(namespace).List(context.TODO(), metav1.L
cmd/flagger/main.go:412 — _, err = flaggerClient.FlaggerV1beta1().MetricTemplates(namespace).List(context.TODO(), me
cmd/flagger/main.go:417 — _, err = flaggerClient.FlaggerV1beta1().AlertProviders(namespace).List(context.TODO(), met
pkg/canary/config_tracker.go:79 — config, err := ct.KubeClient.CoreV1().ConfigMaps(namespace).Get(context.TODO(), name, meta
pkg/canary/config_tracker.go:98 — secret, err := ct.KubeClient.CoreV1().Secrets(namespace).Get(context.TODO(), name, metav1.

Security & Reliability Posture

strong
05.27

The build runs third-party code it does not pin

adequate

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

Evidence
.github/workflows/release.yml:34 — action pinned by tag
.github/workflows/release.yml:107 — action pinned by tag
05.65

1 advisory against this project in the last 24 months, 1 high or critical

adequate

The newest was published on 2026-09-23. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 1 record names flagger with nothing tying it to this repository (CVE-2026-1854).

Evidence
2026-09-23: GHSA-c2p2-jpmj-qvr2 (critical), fixed in 1.45.0: Flagger externalmetrics MetricTemplate provider address can leak the operator ServiceAccount token

Observability & Operations

strong
06.9

No error reporter is wired in

adequate

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.

Evidence
no error reporter initialised

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on fluxcd/flagger: 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.