facebook/hhvm

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.

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

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 140.12s for a 543.2 MB repo slow.
Repobility's analysis ran in 499.23s after the clone landed.

https://github.com/facebook/hhvm · scanned 2026-06-05 18:10 UTC (4 days, 20 hours ago) · 10 languages

946 raw signals (240 security + 706 graph) 11/13 scanners ran System graph score 54 (higher by 20)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 20 hours ago · v2 · 282 actionable findings from 2 signal sources. 286 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 · 215 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`	80.0	0.20	16.00
`documentation_score`	88.0	0.15	13.20
`practices_score`	50.0	0.15	7.50
`code_quality`	68.0	0.10	6.80
Overall		1.00	74.5

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 4 High 21 Medium 25 Low 157 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 67 System graph 215 Crowd 0 Layer: Quality 162 Cicd 14 Software 75 Frontend 10 Hardware 8 Security 9 Api 4

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 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 6 places

View all duplicates & near-duplicates findings →

Legacy markers 2 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

2 matching findings on this repo

low Old/deprecated-named symbol `types_legacy` in third-party/fb-mysql/8.0.20/extra…
low Old/deprecated-named symbol `_warn_if_legacy` in third-party/thrift/src/thrift/…

View all legacy markers findings →

Commented-out code 27 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 (5 lines) in third-party/mcrouter/src/mcrouter/test/test_d…
info Commented-code block (5 lines) in third-party/mcrouter/src/mcrouter/test/test_r…
info Commented-code block (8 lines) in third-party/folly/src/folly/coro/scripts/co_b…
info Commented-code block (5 lines) in third-party/folly/src/folly/fibers/scripts/gd…
info Commented-code block (6 lines) in third-party/fb-mysql/8.0.20/extra/duktape/duk…
info Commented-code block (6 lines) in third-party/fb-mysql/8.0.20/extra/duktape/duk…
info Commented-code block (5 lines) in third-party/fb-mysql/8.0.20/extra/duktape/duk…
info Commented-code block (5 lines) in third-party/fb-mysql/8.0.20/extra/duktape/duk…
info Commented-code block (5 lines) in third-party/fb-mysql/8.0.20/extra/duktape/duk…
info Commented-code block (6 lines) in third-party/fb-mysql/8.0.20/extra/duktape/duk…
info Commented-code block (5 lines) in third-party/fb-mysql/8.0.20/extra/duktape/duk…
info Commented-code block (6 lines) in third-party/fb-mysql/8.0.20/extra/duktape/duk…

View all commented-out code findings →

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

12 matching findings on this repo

medium No CI/CD configuration found
high [MINED106] Phantom test coverage: test_bad_config: Test function `test_bad_conf… third-party/mcrouter/src/mcrouter/test/test_bad_p…:58
low File has no detected symbols: third-party/watchman/src/website/babel.config.js
low File has no detected symbols: third-party/watchman/src/website/docusaurus.confi…
high Insecure pattern 'eval_used' in third-party/fb-mysql/8.0.20/extra/duktape/dukta… third-party/fb-mysql/8.0.20/extra/duktape/duktape…:10
high Insecure pattern 'eval_used' in third-party/fb-mysql/8.0.20/extra/duktape/dukta… third-party/fb-mysql/8.0.20/extra/duktape/duktape…:8
critical Possible secret in third-party/watchman/src/website/docusaurus.config.js third-party/watchman/src/website/docusaurus.confi…:239
low Very large file: third-party/fb-mysql/8.0.20/extra/duktape/duktape-2.3.0/tools/…
low Old/deprecated-named symbol `test_dumped_config_too_old` in third-party/mcroute…
info Commented-code block (5 lines) in third-party/fb-mysql/8.0.20/extra/duktape/duk…
low Old/deprecated-named symbol `types_legacy` in third-party/fb-mysql/8.0.20/extra…
info Commented-code block (6 lines) in third-party/fb-mysql/8.0.20/extra/duktape/duk…

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/4717a4c5-1b58-4d0c-83a5-90f6bd950c54/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4717a4c5-1b58-4d0c-83a5-90f6bd950c54/

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.