facebook/folly

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.

108 of your 117 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.54s · analysis 19.78s · 28.2 MB · GitHub preflight 412ms

https://github.com/facebook/folly · scanned 2026-06-06 00:34 UTC (4 days, 2 hours ago) · 10 languages

222 raw signals (112 security + 110 graph) 11/13 scanners ran System graph score 90 (lower by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 21 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`	77.0	0.20	15.40
`documentation_score`	80.0	0.15	12.00
`practices_score`	67.0	0.15	10.05
`code_quality`	69.0	0.10	6.90
Overall		1.00	75.4

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 0 High 4 Medium 7 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 39 System graph 21 Crowd 0 Layer: Quality 46 Software 6 Cicd 5 Api 1 Frontend 1 Security 1

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

3 matching findings on this repo

low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

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

2 matching findings on this repo

info Commented-code block (8 lines) in folly/coro/scripts/co_bt.py:370
info Commented-code block (5 lines) in folly/fibers/scripts/gdb.py:237

View all commented-out code 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/fcd61328-6233-4daa-b026-efc81e3e5c28/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fcd61328-6233-4daa-b026-efc81e3e5c28/

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.