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.
Sign up free Scan another repo

mohamad186466/WordPress

https://github.com/mohamad186466/WordPress · scanned 2026-09-02 22:18 UTC (1 week, 2 days ago)

163 raw signals (0 security + 163 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 2 days ago · v1 · 163 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
89.3
/100
Security checks
89
0 findings
System graph
89
90.0% cov · 163 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 42 Medium 45 Low 56 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 163 Crowd 0 Layer: Frontend 41 Security 33 Quality 32 Dependencies 57

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.MEDIUM Layer.SECURITY score 0.450
Why: medium 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
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
#3
Insecure pattern 'new_function_used' in wp-includes/js/colorpicker.min.js:2
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
wp-includes/js/colorpicker.min.js:2
#4
Insecure pattern 'new_function_used' in wp-includes/js/underscore.js:951
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
wp-includes/js/underscore.js:951
#5
Insecure pattern 'new_function_used' in wp-includes/js/underscore.min.js:2
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
wp-includes/js/underscore.min.js:2
#6
Insecure pattern 'new_function_used' in wp-includes/js/colorpicker.js:413
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
wp-includes/js/colorpicker.js:413
#7
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
#8
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
#9
Vulnerable dependency postcss 8.5.6: GHSA-6g55-p6wh-862q
GapSeverity.HIGH Layer.DEPENDENCIES score 0.375
Why: high severity
wp-content/themes/twentynineteen/package.json
#10
Vulnerable dependency postcss 8.5.6: GHSA-r28c-9q8g-f849
GapSeverity.HIGH Layer.DEPENDENCIES score 0.375
Why: high severity
wp-content/themes/twentynineteen/package.json

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/c82c46e7-362b-4cbf-91ce-0303e694eef7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c82c46e7-362b-4cbf-91ce-0303e694eef7/

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.