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
31 of your 112 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 65.26s for a 84.5 MB repo slow.
  • Repobility's analysis ran in 27.31s after the clone landed.

wordpress/wordpress

https://github.com/wordpress/wordpress · scanned 2026-06-04 23:22 UTC (10 hours, 38 minutes ago) · 10 languages

417 findings (87 legacy + 330 scanner) 11/13 scanners ran Scanner says 73 (lower by 22)

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

Complete repo analysis

Last scanned 10 hours, 37 minutes ago · v2 · 252 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
Combined
68.6
/100
Repobility
64
87 legacy
9-layer
73
100.0% cov · 165 gaps
Critical
5
click to filter
Agents
6
0 votes
Crowd
0
reported
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 60.0 0.15 9.00
practices_score 30.0 0.15 4.50
code_quality 70.0 0.10 7.00
Overall 1.00 51.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 5 High 41 Medium 29 Low 121 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 87 9-layer 165 Crowd 0 Layer: Quality 129 Security 21 Software 57 Frontend 43 Cicd 1 Api 1

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.

Fragile runtime 85 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium Vendored upstream framework tree is mixed with application code wp-includes:1
  • medium Vendored upstream framework tree is mixed with application code wp-admin:1
  • medium [SEC087] JS: weak Math.random for crypto: Math.random() is not cryptographicall… wp-includes/js/wp-embed.js:99
  • medium [SEC134] AI scaffold leftover — Lorem ipsum / example.com / John Doe in code: L… wp-content/themes/twentyeleven/inc/block-patterns…:125
  • low Duplicated implementation block across source files wp-content/themes/twentyfourteen/content-link.php:1
  • low Duplicated implementation block across source files wp-content/themes/twentyfourteen/content-image.php:1
  • low Duplicated implementation block across source files wp-content/themes/twentyfourteen/content-gallery.…:1
  • low Duplicated implementation block across source files wp-content/themes/twentyfourteen/content-audio.php:1
  • low Duplicated implementation block across source files wp-content/themes/twentyfourteen/category.php:19
  • low Duplicated implementation block across source files wp-content/themes/twentyfourteen/author.php:19
  • low Duplicated implementation block across source files wp-content/themes/twentyfifteen/search.php:19
  • low Duplicated implementation block across source files wp-content/themes/twentyfifteen/index.php:11
View all fragile runtime findings →
Legacy markers 3 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.
3 matching findings on this repo
  • low Legacy-named symbol `actions_copy` in wp-includes/js/clipboard.js:139
  • low Legacy-named symbol `pdataOld` in wp-includes/js/jquery/jquery.js:5819
  • low Legacy-named symbol `pg_end_copy` in wp-includes/js/codemirror/codemirror.min.j…
View all legacy markers findings →
Commented-out code 14 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 wp-includes/js/backbone.js:1095
  • info Commented-code block (5 lines) in wp-includes/js/underscore.js:59
  • info Commented-code block (6 lines) in wp-includes/js/hoverIntent.js:133
  • info Commented-code block (10 lines) in wp-includes/js/colorpicker.js:10
  • info Commented-code block (7 lines) in wp-includes/js/jquery/jquery.js:17
  • info Commented-code block (9 lines) in wp-includes/js/jquery/jquery-migrate.js:65
  • info Commented-code block (5 lines) in wp-includes/js/jquery/jquery.hotkeys.js:81
  • info Commented-code block (6 lines) in wp-includes/js/jquery/ui/autocomplete.js:223
  • info Commented-code block (8 lines) in wp-includes/js/jquery/ui/dialog.js:884
  • info Commented-code block (5 lines) in wp-includes/js/jquery/ui/spinner.js:169
  • info Commented-code block (5 lines) in wp-includes/js/jquery/ui/tooltip.js:239
  • info Commented-code block (7 lines) in wp-includes/js/jquery/ui/sortable.js:959
View all commented-out code findings →
Config drift 2 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.
2 matching findings on this repo
  • medium No CI/CD configuration found
  • high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… wp-includes/js/wp-sanitize.js:30
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/6d531520-742c-4cc2-8f61-486e8f74ff8a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/6d531520-742c-4cc2-8f61-486e8f74ff8a/

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.