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.

SidraChain/blockscout-frontend

https://github.com/SidraChain/blockscout-frontend · scanned 2026-10-15 12:56 UTC (1 week, 4 days ago)

622 raw signals (0 security + 622 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 4 days ago · v1 · 622 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 622 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 174 Medium 349 Low 53 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 622 Crowd 0 Layer: Frontend 50 Security 433 Quality 33 Hardware 2 Cicd 1 Dependencies 98 Api 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 4 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/`.

4 matching findings on this repo

info Commented-code block (24 lines) in ui/userOp/UserOpSubHeading.tsx:57 ui/userOp/UserOpSubHeading.tsx:57
info Commented-code block (7 lines) in ui/pages/ValidatorsStability.tsx:67 ui/pages/ValidatorsStability.tsx:67
info Commented-code block (6 lines) in ui/tx/TxInternals.tsx:55 ui/tx/TxInternals.tsx:55
info Commented-code block (5 lines) in public/static/capibara/index.js:303 public/static/capibara/index.js:303

View all commented-out code findings →

Config drift 41 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

high CVE-2026-48779: ws 8.18.3 — deploy/tools/essential-dapps-chains-config-generato…
medium CVE-2026-45736: ws 8.18.3 — deploy/tools/essential-dapps-chains-config-generato…
medium Runtime dotenv file present in repo: configs/envs/.env.main configs/envs/.env.main
medium Runtime dotenv file present in repo: configs/envs/.env.neon_devnet configs/envs/.env.neon_devnet
medium Runtime dotenv file present in repo: configs/envs/.env.eth_sepolia configs/envs/.env.eth_sepolia
medium Runtime dotenv file present in repo: configs/envs/.env.rootstock_testnet configs/envs/.env.rootstock_testnet
medium Runtime dotenv file present in repo: configs/envs/.env.pw configs/envs/.env.pw
medium Runtime dotenv file present in repo: configs/envs/.env.optimism configs/envs/.env.optimism
medium Runtime dotenv file present in repo: configs/envs/.env.garnet configs/envs/.env.garnet
medium Runtime dotenv file present in repo: configs/envs/.env.polygon configs/envs/.env.polygon
medium Runtime dotenv file present in repo: configs/envs/.env.arbitrum_nova configs/envs/.env.arbitrum_nova
medium Runtime dotenv file present in repo: configs/envs/.env.gnosis configs/envs/.env.gnosis

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/47fd2768-aaf7-41d1-8bb9-34854e5b2338/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/47fd2768-aaf7-41d1-8bb9-34854e5b2338/

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.