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

Scan timing: clone 13.3s · analysis 27.67s · 36.1 MB · GitHub API rate-limit (preflight)

facebook/react

https://github.com/facebook/react · scanned 2026-06-05 04:28 UTC (9 hours, 32 minutes ago) · 10 languages

2383 findings (123 legacy + 2260 scanner) 11/13 scanners ran 86th percentile · Javascript · large (100-500K LoC) Scanner says 41 (higher by 50)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 9 hours, 32 minutes ago · v2 · 1253 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 95.0 0.20 19.00
documentation_score 99.0 0.15 14.85
practices_score 100.0 0.15 15.00
code_quality 80.0 0.10 8.00
Overall 1.00 90.8
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 compiler/packages/react-mcp-server/src/utils/algolia.ts
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 compiler/packages/react-mcp-server/src/utils/algolia.ts:14; move to env var / secrets manager.
compiler/packages/react-mcp-server/src/utils/algolia.ts:14
#2
.env file present in repo: fixtures/fiber-debugger/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#3
.env file present in repo: fixtures/nesting/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#4
Insecure pattern 'eval_used' in compiler/packages/snap/src/sprout/evaluator.ts:255
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
compiler/packages/snap/src/sprout/evaluator.ts:255
#5
Insecure pattern 'eval_used' in fixtures/fiber-debugger/src/App.js:122
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
fixtures/fiber-debugger/src/App.js:122
#6
Insecure pattern 'exec_used' in scripts/devtools/publish-release.js:107
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/devtools/publish-release.js:107
#7
Insecure pattern 'exec_used' in scripts/devtools/utils.js:90
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/devtools/utils.js:90
#8
Insecure pattern 'exec_used' in scripts/devtools/build-and-test.js:72
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/devtools/build-and-test.js:72
#9
Insecure pattern 'exec_used' in scripts/devtools/prepare-release.js:85
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/devtools/prepare-release.js:85
#10
Insecure pattern 'exec_used' in scripts/shared/listChangedFiles.js:40
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/shared/listChangedFiles.js:40

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/71490123-d37f-4659-ac2a-5b9a11374c25/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/71490123-d37f-4659-ac2a-5b9a11374c25/

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.