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.

payloadcms/payload

https://github.com/payloadcms/payload · scanned 2026-05-16 13:37 UTC (1 day, 7 hours ago) · 10 languages

1367 findings (172 legacy + 1195 scanner) 8/10 scanners ran 17th percentile · Typescript · huge (>500K LoC)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 days, 4 hours ago · v1 · 1365 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. #}
Score breakdown â 2026-05-17-v4 calibration-aware
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 23.7 0.25 5.92
testing_score 95.0 0.20 19.00
documentation_score 74.0 0.15 11.10
practices_score 75.0 0.15 11.25
code_quality 80.0 0.10 8.00
Overall 1.00 68.0
Calibrated penalty buckets (security_score): web: 3.0 · authz: 10.6 · docker: 140.4 · threat: 12.8 · journey: 44.4
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 packages/payload/src/collections/operations/utilities/types.ts
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 packages/payload/src/collections/operations/utilities/types.ts:186; move to env var / secrets manager.
packages/payload/src/collections/operations/utilities/types.ts:186
#2
Possible secret in packages/payload/src/collections/operations/utilities/types.ts
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 packages/payload/src/collections/operations/utilities/types.ts:191; move to env var / secrets manager.
packages/payload/src/collections/operations/utilities/types.ts:191
#3
Possible secret in packages/db-mongodb/src/testCredentials.ts
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 packages/db-mongodb/src/testCredentials.ts:2; move to env var / secrets manager.
packages/db-mongodb/src/testCredentials.ts:2
#4
Possible secret in packages/translations/src/languages/hy.ts
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 packages/translations/src/languages/hy.ts:14; move to env var / secrets manager.
packages/translations/src/languages/hy.ts:14
#5
Possible secret in packages/translations/src/languages/hy.ts
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 packages/translations/src/languages/hy.ts:18; move to env var / secrets manager.
packages/translations/src/languages/hy.ts:18
#6
Possible secret in packages/translations/src/languages/hy.ts
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 packages/translations/src/languages/hy.ts:27; move to env var / secrets manager.
packages/translations/src/languages/hy.ts:27
#7
Possible secret in packages/translations/src/languages/hy.ts
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 packages/translations/src/languages/hy.ts:40; move to env var / secrets manager.
packages/translations/src/languages/hy.ts:40
#8
Possible secret in packages/translations/src/languages/hy.ts
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 packages/translations/src/languages/hy.ts:56; move to env var / secrets manager.
packages/translations/src/languages/hy.ts:56
#9
Possible secret in packages/translations/src/languages/hy.ts
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 packages/translations/src/languages/hy.ts:59; move to env var / secrets manager.
packages/translations/src/languages/hy.ts:59
#10
Possible secret in packages/translations/src/languages/hy.ts
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 packages/translations/src/languages/hy.ts:62; move to env var / secrets manager.
packages/translations/src/languages/hy.ts:62

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/836245fa-286f-4238-953c-95e0eac60349/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/836245fa-286f-4238-953c-95e0eac60349/

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.