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

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

Runtime dotenv file present in repo: configs/envs/.env.celo_sepolia

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 configs/envs/.env.celo_sepolia; move to env var / secrets manager.

configs/envs/.env.celo_sepolia

Runtime dotenv file present in repo: configs/envs/.env.celo

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 configs/envs/.env.celo; move to env var / secrets manager.

configs/envs/.env.celo

Possible secret in stubs/account.ts

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in stubs/account.ts:53; move to env var / secrets manager.

stubs/account.ts:53

CVE-2026-75604: next 15.5.10 — yarn.lock

GapSeverity.CRITICAL Layer.SECURITY score 0.500

Why: critical severity

GHSA-2xp9-vwfh-vxw4: next 15.5.10 — yarn.lock

GapSeverity.CRITICAL Layer.SECURITY score 0.500

Why: critical severity

CVE-2026-41242: protobufjs 7.2.5 — yarn.lock

GapSeverity.CRITICAL Layer.SECURITY score 0.500

Why: critical severity

CVE-2026-41242: protobufjs 7.3.2 — yarn.lock

GapSeverity.CRITICAL Layer.SECURITY score 0.500

Why: critical severity

Runtime dotenv file present in repo: configs/envs/.env.main

GapSeverity.MEDIUM Layer.SECURITY score 0.450

Why: medium severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in configs/envs/.env.main; move to env var / secrets manager.

configs/envs/.env.main

Runtime dotenv file present in repo: configs/envs/.env.neon_devnet

GapSeverity.MEDIUM Layer.SECURITY score 0.450

Why: medium severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in configs/envs/.env.neon_devnet; move to env var / secrets manager.

configs/envs/.env.neon_devnet

#10

Runtime dotenv file present in repo: configs/envs/.env.eth_sepolia

GapSeverity.MEDIUM Layer.SECURITY score 0.450

Why: medium severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in configs/envs/.env.eth_sepolia; move to env var / secrets manager.

configs/envs/.env.eth_sepolia

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