controlplaneio-fluxcd/flux-operator

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

34 of your 163 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.6s · analysis 19.71s · 22.3 MB · GitHub API rate-limit (preflight)

https://github.com/controlplaneio-fluxcd/flux-operator · scanned 2026-06-05 21:09 UTC (4 days, 12 hours ago) · 10 languages

313 raw signals (155 security + 158 graph) 45th percentile · Go · large (100-500K LoC) System graph score 77 (lower by 5)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 12 hours ago · v2 · 171 actionable findings from 2 signal sources. 63 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 72 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	47.6	0.25	11.90
`testing_score`	85.0	0.20	17.00
`documentation_score`	76.0	0.15	11.40
`practices_score`	94.0	0.15	14.10
`code_quality`	47.6	0.10	4.76
Overall		1.00	71.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 8 High 47 Medium 25 Low 62 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 99 System graph 72 Crowd 0 Layer: Software 110 Cicd 4 Quality 35 Security 14 Api 1 Frontend 2 Hardware 5

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 1 finding

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

1 matching finding on this repo

info Commented-code block (6 lines) in web/src/components/dashboards/resource/Invent…

View all commented-out code findings →

Config drift 6 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

6 matching findings on this repo

high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… internal/lkm/fetch.go:131
low File has no detected symbols: web/vite.config.js
low File has no detected symbols: web/tailwind.config.js
low File has no detected symbols: web/eslint.config.js
low File has no detected symbols: web/postcss.config.js
low Very large file: internal/controller/resourceset_controller_configs_test.go (16…

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/f104ae14-dc29-43fb-b60b-d9c0168d1d86/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f104ae14-dc29-43fb-b60b-d9c0168d1d86/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.