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.

WordPress/WordPress-Develop

https://github.com/WordPress/WordPress-Develop.git · scanned 2026-05-16 13:30 UTC (1 day, 6 hours ago) · 10 languages

121 findings (29 legacy + 92 scanner) 8/10 scanners ran Scanner says 70 (lower by 12)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 10 hours ago · v1 · 112 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
{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
4 healthy
Wp Site Health V1 Directory Sizes page
healthy
page
auth
Wp V2 Users Me Application Passwords Locale User page
healthy
page
auth
Wp V2 Users Me Application Passwords page
healthy
page
auth
Wp V2 Users page
healthy
page
auth
{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/17978a6a-1088-4d9a-a761-73a403ca6a42/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/17978a6a-1088-4d9a-a761-73a403ca6a42/

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.