payloadcms/payload

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.

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)

File as issue Image

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

100.0% cov · 1195 gaps

{# ── 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: layer: network × excluding tests × Reset all

Scan summary Repository scanned at 67.4/100 with 100.0% coverage. It contains 17048 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 1195 findings — concentrated in security (612), frontend (299), quality (205). Risk profile is high: 603 critical, 3 high, 120 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 1 of 1365 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium 9-layer network security conf 1.00 Privileged port 465 in use

Port 465 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

packages/payload-cloud/src/email.ts securityports

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