WordPress/WordPress-Develop — Repobility public scan

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

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)

File as issue Image

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

100.0% cov · 92 gaps

click to filter

{# ── 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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1

Possible secret in .devcontainer/setup.sh

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 .devcontainer/setup.sh:18; move to env var / secrets manager.

.devcontainer/setup.sh:18

#2

Possible secret in src/js/_enqueues/admin/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 src/js/_enqueues/admin/auth-app.js:84; move to env var / secrets manager.

src/js/_enqueues/admin/auth-app.js:84

#3

Privileged port 256 in use

GapSeverity.MEDIUM Layer.NETWORK score 0.338

Why: medium severity · misconfigured network surface

Fix: If the number in .github/workflows/reusable-workflow-lint.yml is a real port, change the binding to ≥1024 or run behind a proxy.

.github/workflows/reusable-workflow-lint.yml

#4

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/props-bot.yml:74

#5

GitHub Actions workflow grants broad write permissions

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/commit-built-file-changes.yml

#6

`fetch()` without try/.catch or AbortSignal — src/js/media/models/attachment.js:30

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/js/media/models/attachment.js:30, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

#7

`fetch()` without try/.catch or AbortSignal — src/js/media/models/query.js:115

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/js/media/models/query.js:115, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

#8

`fetch()` without try/.catch or AbortSignal — src/js/media/models/post-image.js:28

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/js/media/models/post-image.js:28, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

#9

`fetch()` without try/.catch or AbortSignal — src/js/media/controllers/featured-image.js:114

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/js/media/controllers/featured-image.js:114, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

#10

`fetch()` without try/.catch or AbortSignal — src/js/media/routers/manage.js:56

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/js/media/routers/manage.js:56, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

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.

{# ── 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.