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

WordPress/WordPress

https://github.com/WordPress/WordPress.git · scanned 2026-05-19 20:21 UTC (2 weeks, 2 days ago) · 10 languages

360 findings (30 legacy + 330 scanner) 11/13 scanners ran Scanner says 73 (lower by 23)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 2 days ago · v2 · 195 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 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 0.0 0.20 0.00
documentation_score 68.0 0.15 10.20
practices_score 30.0 0.15 4.50
code_quality 50.0 0.10 5.00
Overall 1.00 50.7
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 wp-admin/js/auth-app.min.js
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 wp-admin/js/auth-app.min.js:2; move to env var / secrets manager.
wp-admin/js/auth-app.min.js:2
#2
Possible secret in wp-admin/js/auth-app.js
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 wp-admin/js/auth-app.js:84; move to env var / secrets manager.
wp-admin/js/auth-app.js:84
#3
Insecure pattern 'eval_used' in wp-includes/js/tw-sack.js:119
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
wp-includes/js/tw-sack.js:119
#4
Insecure pattern 'eval_used' in wp-includes/js/jquery/jquery.form.min.js:1
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
wp-includes/js/jquery/jquery.form.min.js:1
#5
Insecure pattern 'eval_used' in wp-includes/js/jquery/jquery.schedule.js:30
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
wp-includes/js/jquery/jquery.schedule.js:30
#6
Insecure pattern 'eval_used' in wp-includes/js/tinymce/tiny_mce_popup.js:192
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
wp-includes/js/tinymce/tiny_mce_popup.js:192
#7
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#8
Insecure pattern 'cors_wildcard' in wp-includes/js/plupload/moxie.min.js:1
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
wp-includes/js/plupload/moxie.min.js:1
#9
Insecure pattern 'cors_wildcard' in wp-includes/js/mediaelement/mediaelement-and-player.min.js:12
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
wp-includes/js/mediaelement/mediaelement-and-player.min.js:12
#10
Insecure pattern 'cors_wildcard' in wp-includes/js/mediaelement/mediaelement.min.js:12
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
wp-includes/js/mediaelement/mediaelement.min.js:12

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/842b92bb-cdc9-4ae2-b442-6dbe6d93917f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/842b92bb-cdc9-4ae2-b442-6dbe6d93917f/

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.