google/oss-fuzz

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)

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)

File as issue Image

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

100.0% cov · 1504 findings

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

Severity: Critical 8 High 38 Medium 1400 Low 115 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 134 System graph 1504 Crowd 0 Layer: Software 41 Quality 178 Cicd 17 Security 23 Frontend 12 Network 4 Hardware 1358 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.

Duplicates & near-duplicates 10 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

10 matching findings on this repo

low Near-duplicate function bodies in 80 places
low Near-duplicate function bodies in 24 places
low Near-duplicate function bodies in 11 places
low Near-duplicate function bodies in 152 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 32 places
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 16 places
low Near-duplicate function bodies in 8 places
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

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

12 matching findings on this repo

info Commented-code block (12 lines) in projects/vlc/generate_seeds.py:19
info Commented-code block (14 lines) in tools/vscode-extension/src/commands/cmdRepro…
info Commented-code block (5 lines) in infra/test_repos.py:36
info Commented-code block (5 lines) in infra/templates.py:76
info Commented-code block (5 lines) in infra/base-images/base-builder/bisect_clang.p…
info Commented-code block (6 lines) in infra/base-images/base-builder/sanitizers/pys…
info Commented-code block (11 lines) in infra/base-images/base-builder/sanitizers/py…
info Commented-code block (5 lines) in infra/base-images/base-builder/indexer/clang_…
info Commented-code block (8 lines) in infra/base-images/base-builder/indexer/index_…
info Commented-code block (9 lines) in infra/base-images/base-builder/indexer/utils.…
info Commented-code block (7 lines) in infra/base-images/base-runner/jacoco_report_c…
info Commented-code block (12 lines) in infra/base-images/base-runner/test_all.py:180

View all commented-out code findings →

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

10 matching findings on this repo

high [MINED112] FastAPI PATCH config_utils._is_dry_run has no auth: Handler `_create… infra/cifuzz/test_helpers.py:39
high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… projects/fast-xml-parser/fuzz.js:26
low File has no detected symbols: infra/experimental/mcp/config.py
medium Dockerfile runs as root: projects/apache-commons-configuration/Dockerfile
medium Dockerfile runs as root: projects/configparser/Dockerfile
medium Dockerfile runs as root: projects/iniconfig/Dockerfile
medium Dockerfile runs as root: projects/config-validator/Dockerfile
medium Dockerfile runs as root: projects/libconfig/Dockerfile
medium Dockerfile runs as root: projects/spring-cloud-config/Dockerfile
info Commented-code block (6 lines) in infra/cifuzz/config_utils.py:38

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