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

Scan timing: clone 4.83s · analysis 8.99s · 14.7 MB · GitHub API rate-limit (preflight)

cloudflare/agents

https://github.com/cloudflare/agents · scanned 2026-05-24 01:20 UTC (1 week, 5 days ago) · 10 languages

3663 findings (99 legacy + 3564 scanner) 38th percentile · Typescript · large (100-500K LoC) Scanner says 55 (higher by 18)

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

Complete repo analysis

Last scanned 1 week, 5 days ago · v7 · 628 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
62.9
/100
Repobility
71
99 legacy
9-layer
55
100.0% cov · 529 gaps
Critical
6
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 80.1 0.25 20.02
testing_score 95.0 0.20 19.00
documentation_score 62.1 0.15 9.31
practices_score 71.0 0.15 10.65
code_quality 49.5 0.10 4.95
Overall 1.00 72.9
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 6 High 174 Medium 136 Low 188 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 99 9-layer 529 Crowd 0 Layer: Security 15 Quality 298 Software 70 Frontend 104 Cicd 11 Api 130

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

#1
Possible secret in packages/ai-chat/e2e/worker.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/ai-chat/e2e/worker.ts:156; move to env var / secrets manager.
packages/ai-chat/e2e/worker.ts:156
#2
Possible secret in packages/shell/src/git/index.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/shell/src/git/index.ts:74; move to env var / secrets manager.
packages/shell/src/git/index.ts:74
#3
Possible secret in packages/shell/src/git/index.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/shell/src/git/index.ts:258; move to env var / secrets manager.
packages/shell/src/git/index.ts:258
#4
Possible secret in packages/shell/src/git/index.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/shell/src/git/index.ts:294; move to env var / secrets manager.
packages/shell/src/git/index.ts:294
#5
Possible secret in packages/shell/src/git/index.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/shell/src/git/index.ts:323; move to env var / secrets manager.
packages/shell/src/git/index.ts:323
#6
GitHub Action tracks a moving branch
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/bonk.yml:27
#7
`dangerouslySetInnerHTML` used in a React component — examples/playground/src/components/CodeExplanation.tsx:61
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#8
Dangling fetch: GET https://api.openai.com/v1/responses/${responseId} (experimental/forever-chat/src/server.ts:249)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#9
Dangling fetch: GET http://localhost/ (openai-sdk/chess-app/src/index.ts:7)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#10
Dangling fetch: POST https://localhost/v1/devtools/browser (packages/agents/src/browser/shared.ts:160)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.

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.

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/3b58000f-bd23-4495-babe-c5bc135de534/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3b58000f-bd23-4495-babe-c5bc135de534/

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.