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.
269 of your 4448 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 18.97s · analysis 20.52s · 49.8 MB · GitHub API rate-limit (preflight)

google/oss-fuzz

https://github.com/google/oss-fuzz · scanned 2026-06-05 14:28 UTC (5 days, 5 hours ago) · 10 languages

10219 raw signals (4417 security + 5802 graph) 11/13 scanners ran 41st percentile · Python · large (100-500K LoC) System graph score 54 (higher by 19)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 5 hours ago · v2 · 1638 actionable findings from 2 signal sources. 5654 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 46.0 0.20 9.20
documentation_score 100.0 0.15 15.00
practices_score 79.0 0.15 11.85
code_quality 61.0 0.10 6.10
Overall 1.00 73.1
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

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

#1
Possible secret in projects/spring-security/InMemoryUserDetailsManagerChangePasswordFuzzer.java
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 projects/spring-security/InMemoryUserDetailsManagerChangePasswordFuzzer.java:34; move to env var / secrets manager.
projects/spring-security/InMemoryUserDetailsManagerChangePasswordFuzzer.java:34
#2
Possible secret in projects/h2database/TestServer.java
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 projects/h2database/TestServer.java:13; move to env var / secrets manager.
projects/h2database/TestServer.java:13
#3
Possible secret in projects/h2database/TestServer.java
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 projects/h2database/TestServer.java:55; move to env var / secrets manager.
projects/h2database/TestServer.java:55
#4
Possible secret in projects/h2database/TestServer.java
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 projects/h2database/TestServer.java:68; move to env var / secrets manager.
projects/h2database/TestServer.java:68
#5
Flask mutation route `post_json` without `@login_required` — projects/flask/fuzz_json.py:35
GapSeverity.HIGH Layer.SECURITY score 0.525
Why: high severity · OWASP-class risk
Fix: Add `@login_required` decorator above the route function in projects/flask/fuzz_json.py:35.
projects/flask/fuzz_json.py:35
#6
Insecure pattern 'eval_used' in projects/asteval/fuzz_eval.py:31
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
projects/asteval/fuzz_eval.py:31
#7
Blocking `time.sleep(...)` inside `async def run_agent_loop` — infra/experimental/mcp/client.py:204
GapSeverity.HIGH Layer.QUALITY score 0.394
Why: high severity · crashes are likely without this
Fix: Add a `timeout=N` argument and wrap in `try/except` in infra/experimental/mcp/client.py:204 to prevent hung calls.
infra/experimental/mcp/client.py:204
#8
Dockerfile pipes a remote installer into a shell
GapSeverity.HIGH Layer.HARDWARE score 0.375
Why: high severity
projects/unblob/Dockerfile:20
#9
Dockerfile pipes a remote installer into a shell
GapSeverity.HIGH Layer.HARDWARE score 0.375
Why: high severity
projects/cryptography/Dockerfile:22
#10
Dockerfile pipes a remote installer into a shell
GapSeverity.HIGH Layer.HARDWARE score 0.375
Why: high severity
projects/orjson/Dockerfile:25

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/22b9aba9-65f4-441a-acc2-731e6f06fa5a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/22b9aba9-65f4-441a-acc2-731e6f06fa5a/

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.