facebook/flow

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.

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

Scan timing: clone 19.73s · analysis 57.14s · 76.9 MB · GitHub API rate-limit (preflight)

https://github.com/facebook/flow · scanned 2026-06-06 00:54 UTC (4 days, 1 hour ago) · 10 languages

1137 raw signals (137 security + 1000 graph) 11/13 scanners ran 88th percentile · Javascript · huge (>500K LoC) System graph score 52 (higher by 38)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 488 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	72.0	0.15	10.80
`code_quality`	70.0	0.10	7.00
Overall		1.00	90.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 7 High 11 Medium 26 Low 255 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 48 System graph 488 Crowd 0 Layer: Quality 270 Security 12 Cicd 5 Software 53 Frontend 180 Network 16

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.

Legacy markers 4 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.

4 matching findings on this repo

low Old/deprecated-named symbol `invalid_neg_octal_legacy` in tests/bigint/invalid1…
low Old/deprecated-named symbol `invalid_octal_legacy` in tests/bigint/invalid13.js…
low Old/deprecated-named symbol `InvalidOctalLegacy` in tests/bigint/invalid11.js:1
low Old/deprecated-named symbol `InvalidNegOctalLegacy` in tests/bigint/invalid12.j…

View all legacy markers findings →

Commented-out code 100 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 (8 lines) in tests/override/no_implicit_override_off.js:1
info Commented-code block (5 lines) in tests/override/cross_module_static.js:1
info Commented-code block (6 lines) in tests/override/abstract_override.js:4
info Commented-code block (5 lines) in tests/override/accessor_half_pair.js:6
info Commented-code block (5 lines) in tests/ts_variance/tuple_polarity.ts:1
info Commented-code block (5 lines) in tests/ts_variance/cross_lang_lib.ts:1
info Commented-code block (5 lines) in tests/ts_variance/method_bivariance_consumer.…
info Commented-code block (5 lines) in tests/ts_variance/cross_lang_consumer.js:1
info Commented-code block (6 lines) in tests/ts_variance/declared_polarity.ts:6
info Commented-code block (5 lines) in tests/ts_variance/type_arg_variance.ts:22
info Commented-code block (5 lines) in tests/ts_variance/method_bivariance.ts:11
info Commented-code block (8 lines) in tests/ts_variance/optional_property_invarianc…

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

low File has no detected symbols: tests/config_module_file_exts_precedence/js_vs_zz…
low File has no detected symbols: tests/config_module_file_exts_precedence/test.js
low File has no detected symbols: tests/config_module_file_exts_precedence/zzz_vs_z…
low File has no detected symbols: tests/config_module_file_exts_precedence/js_vs_zz…
low File has no detected symbols: tests/config_module_file_exts_precedence/aaa_vs_a…
low File has no detected symbols: tests/config_module_file_exts_precedence/multiple…
critical Possible secret in website/docusaurus.config.js website/docusaurus.config.js:105
low Very large file: rust_port/crates/flow_config/src/flowconfig.rs (3872 lines)
info Commented-code block (7 lines) in packages/babel.config.js:38
info Commented-code block (5 lines) in packages/flow-dev-tools/src/check-test/checkT…

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/4930b5ba-4f83-4e87-9857-7da8af461489/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4930b5ba-4f83-4e87-9857-7da8af461489/

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.