ethereum/go-ethereum

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.

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

Scan timing: clone 14.31s · analysis 17.12s · 81.9 MB · GitHub API rate-limit (preflight)

https://github.com/ethereum/go-ethereum · scanned 2026-06-05 11:41 UTC (5 days, 11 hours ago) · 10 languages

342 raw signals (118 security + 224 graph) 11/13 scanners ran 67th percentile · Go · large (100-500K LoC) System graph score 67 (higher by 18)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 11 hours ago · v2 · 124 actionable findings from 2 signal sources. 106 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 · 82 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`	85.0	0.20	17.00
`documentation_score`	60.0	0.15	9.00
`practices_score`	99.0	0.15	14.85
`code_quality`	70.0	0.10	7.00
Overall		1.00	85.6

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 7 Medium 12 Low 75 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 42 System graph 82 Crowd 0 Layer: Security 9 Cicd 7 Quality 56 Software 40 Api 1 Frontend 7 Hardware 4

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 7 findings

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.

7 matching findings on this repo

low File has no detected symbols: eth/tracers/js/internal/tracers/4byte_tracer_lega…
low File has no detected symbols: eth/tracers/js/internal/tracers/prestate_tracer_l…
low File has no detected symbols: eth/tracers/js/internal/tracers/noop_tracer_legac…
info TODO/FIXME marker in shipping code — eth/tracers/js/internal/tracers/call_trace…
low Very large file: core/txpool/legacypool/legacypool_test.go (2720 lines)
low Very large file: core/txpool/legacypool/legacypool.go (1861 lines)
low Old/deprecated-named symbol `RabbitLegacy` in internal/jsre/deps/web3.js:10038

View all legacy markers findings →

Commented-out code 2 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/`.

2 matching findings on this repo

info Commented-code block (7 lines) in tests/solidity/truffle-config.js:43
info Commented-code block (7 lines) in internal/jsre/deps/web3.js:12858

View all commented-out code findings →

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

3 matching findings on this repo

low File has no detected symbols: tests/solidity/truffle-config.js
low Very large file: params/config.go (1412 lines)
info Commented-code block (7 lines) in tests/solidity/truffle-config.js:43

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/883bffd4-e24a-4bed-a8ca-09ff79b781d0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/883bffd4-e24a-4bed-a8ca-09ff79b781d0/

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.