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.
Sign up free Scan another repo
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)

electron/electron

https://github.com/electron/electron · scanned 2026-06-05 05:10 UTC (8 hours, 35 minutes ago) · 10 languages

724 findings (92 legacy + 632 scanner) 11/13 scanners ran 21st percentile · Javascript · large (100-500K LoC) Scanner says 72 (lower by 4)

File as issue Image v2 schema
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 8 hours, 35 minutes ago · v2 · 408 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
78.1
/100
Repobility
84
92 legacy
9-layer
72
100.0% cov · 316 gaps
Critical
12
click to filter
Agents
6
0 votes
Crowd
0
reported
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 12 High 33 Medium 38 Low 235 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 92 9-layer 316 Crowd 0 Layer: Quality 158 Cicd 16 Security 13 Software 67 Frontend 153 Hardware 1

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in spec/api-app-spec.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in spec/api-app-spec.ts:533; move to env var / secrets manager.
spec/api-app-spec.ts:533
#2
Insecure pattern 'exec_used' in spec/release-notes-spec.ts:46
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
spec/release-notes-spec.ts:46
#3
Insecure pattern 'exec_used' in spec/version-bump-spec.ts:37
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
spec/version-bump-spec.ts:37
#4
Insecure pattern 'exec_used' in spec/extensions-spec.ts:299
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
spec/extensions-spec.ts:299
#5
Insecure pattern 'eval_used' in spec/chromium-spec.ts:473
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
spec/chromium-spec.ts:473
#6
Insecure pattern 'eval_used' in script/node/generate_node_headers.py:21
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
script/node/generate_node_headers.py:21
#7
Insecure pattern 'subprocess_shell_true' in script/run-clang-format.py:138
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
script/run-clang-format.py:138
#8
Insecure pattern 'weak_hash' in script/codesign/gen-trust.ts:19
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
script/codesign/gen-trust.ts:19
#9
Insecure pattern 'subprocess_shell_true' in script/lib/util.py:224
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
script/lib/util.py:224
#10
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/windows-publish.yml

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.