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

OpenZeppelin/openzeppelin-contracts

https://github.com/OpenZeppelin/openzeppelin-contracts.git · scanned 2026-05-16 13:30 UTC (1 day, 5 hours ago) · 10 languages

83 findings (6 legacy + 77 scanner)

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

Complete repo analysis

Last scanned 1 day, 9 hours ago · v1 · 83 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
89.0
/100
Repobility
91
6 legacy
9-layer
88
66.7% cov · 77 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: severity: high × excluding tests × Reset all
Severity: Critical 0 High 4 Medium 7 Low 64 Source: Legacy 6 9-layer 77 Crowd 0 Layer: Quality 12 Software 41 Api 1 Frontend 9 Security 3 Cicd 17
Scan summary Repository scanned at 87.5/100 with 66.7% coverage. It contains 958 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 77 findings — concentrated in software (39), cicd (17), frontend (9). Risk profile is high: 0 critical, 2 high, 7 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 4 of 83 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high Legacy software ssrf conf 1.00 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTTP request to a user-controlled URL without allowlist validation. Attackers can probe internal services (169.254.169.254 metadata, internal Kubernetes endpoints, file:// URIs), exfiltrate data, or pivot through your network. SSRF is OWASP A10:2021 and a frequent foothold in cloud breaches.
Validate the URL against an allowlist BEFORE fetching: ALLOWED = {'images.example.com', 'cdn.example.com'} host = urlparse(url).hostname if host not in ALLOWED: abort(400) Or use a server-side proxy (Imgproxy / serve-files-only-from-S3) that isolates outbound network access from the request h…
contracts/utils/cryptography/WebAuthn.sol:161 ssrflegacy
high Legacy software ssrf conf 1.00 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTTP request to a user-controlled URL without allowlist validation. Attackers can probe internal services (169.254.169.254 metadata, internal Kubernetes endpoints, file:// URIs), exfiltrate data, or pivot through your network. SSRF is OWASP A10:2021 and a frequent foothold in cloud breaches.
Validate the URL against an allowlist BEFORE fetching: ALLOWED = {'images.example.com', 'cdn.example.com'} host = urlparse(url).hostname if host not in ALLOWED: abort(400) Or use a server-side proxy (Imgproxy / serve-files-only-from-S3) that isolates outbound network access from the request h…
contracts/utils/Base64.sol:27 ssrflegacy
high 9-layer security owasp conf 1.00 Insecure pattern 'exec_used' in fv/run.js:49
Found a known-risky pattern (exec_used). Review and replace if possible.
fv/run.js:49 owaspexec_used
high 9-layer security owasp conf 1.00 Insecure pattern 'exec_used' in scripts/solc-versions.js:11
Found a known-risky pattern (exec_used). Review and replace if possible.
scripts/solc-versions.js:11 owaspexec_used
{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/47a2334c-e2e2-49cc-9087-a4a6fae9320b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/47a2334c-e2e2-49cc-9087-a4a6fae9320b/

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.