rancher-sandbox/rancher-desktop

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.

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

Scan timing: clone 3.71s · analysis 60.83s · 7.4 MB · GitHub preflight 469ms

https://github.com/rancher-sandbox/rancher-desktop · scanned 2026-06-05 18:18 UTC (4 days, 20 hours ago) · 10 languages

996 raw signals (540 security + 456 graph) 12th percentile · Typescript · large (100-500K LoC) System graph score 50 (higher by 13)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 20 hours ago · v2 · 400 actionable findings from 2 signal sources. 368 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 · 214 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	14.7	0.25	3.67
`testing_score`	72.0	0.20	14.40
`documentation_score`	90.7	0.15	13.61
`practices_score`	88.0	0.15	13.20
`code_quality`	58.0	0.10	5.80
Overall		1.00	63.4

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 103 Medium 48 Low 169 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 186 System graph 214 Crowd 0 Layer: Quality 80 Security 10 Software 187 Cicd 11 Frontend 106 Hardware 4 Api 2

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.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `convertToRegistryLegacy` in e2e/utils/TestUtils.ts…

View all legacy markers findings →

Commented-out code 23 findings

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/`.

12 matching findings on this repo

info Commented-code block (5 lines) in scripts/package.ts:175
info Commented-code block (6 lines) in scripts/release-merge-to-main.ts:168
info Commented-code block (5 lines) in scripts/dependencies/wsl.ts:37
info Commented-code block (6 lines) in scripts/dependencies/electron.ts:26
info Commented-code block (7 lines) in scripts/lib/build-utils.ts:115
info Commented-code block (5 lines) in scripts/lib/installer-win32.tsx:103
info Commented-code block (5 lines) in scripts/lib/dependencies.ts:329
info Commented-code block (5 lines) in scripts/lib/sign-macos.ts:191
info Commented-code block (8 lines) in .github/workflows/bats/get-tests.py:3
info Commented-code block (5 lines) in pkg/rancher-desktop/config/settingsImpl.ts:147
info Commented-code block (5 lines) in pkg/rancher-desktop/utils/ipcRenderer.ts:30
info Commented-code block (6 lines) in pkg/rancher-desktop/sudo-prompt/index.js:106

View all commented-out code findings →

Config drift 15 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.

12 matching findings on this repo

low npm package `@vue/eslint-config-typescript` is minor version(s) behind (14.7.0 … package.json
low File has no detected symbols: jest.config.js
low File has no detected symbols: screenshots/playwright-config.ts
low File has no detected symbols: pkg/rancher-desktop/config/emptyStubForJSLinter.js
low File has no detected symbols: pkg/rancher-desktop/config/query-params.js
low File has no detected symbols: pkg/rancher-desktop/config/types.js
low File has no detected symbols: pkg/rancher-desktop/config/cookies.js
low File has no detected symbols: pkg/rancher-desktop/config/__tests__/commandLineO…
low File has no detected symbols: pkg/rancher-desktop/config/__tests__/settingsMigr…
low File has no detected symbols: pkg/rancher-desktop/components/SortableTable/sort…
low Stray `console.log` in TS/JS — pkg/rancher-desktop/config/settingsImpl.ts:76
info TODO/FIXME marker in shipping code — pkg/rancher-desktop/config/__tests__/setti…

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/e1e86596-98e4-49d3-9e75-8c9c146b8cc6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e1e86596-98e4-49d3-9e75-8c9c146b8cc6/

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.