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.
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 30.61s for a 64.3 MB repo slow.
  • Repobility's analysis ran in 19.7s after the clone landed.

vercel/ai

https://github.com/vercel/ai · scanned 2026-05-31 01:27 UTC (5 days, 7 hours ago) · 10 languages

3198 findings (95 legacy + 3103 scanner) 11/13 scanners ran 53rd percentile · Typescript · large (100-500K LoC) Scanner says 69 (higher by 7)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 7 hours ago · v2 · last Δ +5.8 (diff) · 1649 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
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 79.0 0.20 15.80
documentation_score 45.0 0.15 6.75
practices_score 74.0 0.15 11.10
code_quality 79.0 0.10 7.90
Overall 1.00 75.6
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

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

#1
Possible secret in packages/openai/src/responses/__fixtures__/openai-compaction.1.json
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/openai/src/responses/__fixtures__/openai-compaction.1.json:36; move to env var / secrets manager.
packages/openai/src/responses/__fixtures__/openai-compaction.1.json:36
#2
Insecure pattern 'private_key_in_repo' in packages/google-vertex/src/edge/google-vertex-auth-edge.ts:59
GapSeverity.CRITICAL Layer.SECURITY score 0.550
Why: critical severity · OWASP-class risk
packages/google-vertex/src/edge/google-vertex-auth-edge.ts:59
#3
`dangerouslySetInnerHTML` used in a React component — examples/next-openai-kasada-bot-protection/kasada/kasada-client.tsx:7
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#4
Dangling fetch: POST http://localhost:${DEVTOOLS_PORT}/api/notify (packages/devtools/src/db.ts:26)
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.
#5
Dangling fetch: POST https://oauth2.googleapis.com/token (packages/google-vertex/src/edge/google-vertex-auth-edge.ts:139)
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.
#6
Dangling fetch: DELETE /api/chat/${chatData.id}/stream (examples/next/app/chat/[chatId]/chat.tsx:88)
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.
#7
Dangling fetch: DELETE https://api.openai.com/v1/skills/${skillId} (examples/ai-functions/src/lib/delete-uploaded-skill.ts:11)
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.
#8
Dangling fetch: GET /api/generate-node (examples/next-google-vertex/app/node/page.tsx:12)
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 /api/generate-edge (examples/next-google-vertex/app/edge/page.tsx:12)
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 /api/generate-chat (examples/next-openai-pages/pages/chat/generate-chat/index.tsx:45)
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/9a1ae60a-ba5d-47ea-833b-bdc487805b97/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9a1ae60a-ba5d-47ea-833b-bdc487805b97/

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.