electron/electron

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.

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

Scan timing: clone 19.98s · analysis 14.13s · 33.0 MB · GitHub API rate-limit (preflight)

https://github.com/electron/electron · scanned 2026-06-05 05:10 UTC (1 week, 1 day ago) · 10 languages

724 raw signals (92 security + 632 graph) 11/13 scanners ran 38th percentile · Javascript · large (100-500K LoC) System graph score 72 (lower by 4)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 1 day ago · v2 · 348 actionable findings from 2 signal sources. 60 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 · 301 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	0.0	0.20	0.00
`documentation_score`	78.0	0.15	11.70
`practices_score`	72.0	0.15	10.80
`code_quality`	74.0	0.10	7.40
Overall		1.00	67.7

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 8 Medium 30 Low 212 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 47 System graph 301 Crowd 0 Layer: Quality 119 Cicd 6 Security 13 Software 56 Frontend 153 Hardware 1

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.

Duplicates & near-duplicates 2 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Commented-out code 35 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 (8 lines) in spec/api-net-spec.ts:1170
info Commented-code block (6 lines) in spec/api-net-session-spec.ts:357
info Commented-code block (5 lines) in spec/api-browser-window-spec.ts:4087
info Commented-code block (5 lines) in spec/api-session-spec.ts:656
info Commented-code block (5 lines) in spec/api-web-contents-view-spec.ts:248
info Commented-code block (5 lines) in spec/api-js2c-code-cache-spec.ts:8
info Commented-code block (5 lines) in spec/api-power-monitor-spec.ts:1
info Commented-code block (6 lines) in spec/node-spec.ts:218
info Commented-code block (5 lines) in spec/index.js:147
info Commented-code block (8 lines) in spec/api-autoupdater-darwin-spec.ts:479
info Commented-code block (5 lines) in spec/chromium-spec.ts:692
info Commented-code block (6 lines) in spec/api-app-spec.ts:552

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

low [COMP001] High cognitive complexity: Function `apply_config` has cognitive comp… script/apply_all_patches.py:41

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/2a0b265b-a401-44a3-aadc-b28d2331293f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2a0b265b-a401-44a3-aadc-b28d2331293f/

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.