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.

Scan timing: clone 1.61s · analysis 4.66s · 6.7 MB · GitHub API rate-limit (preflight)

openai/openai-node

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

1400 findings (66 legacy + 1334 scanner) 90th percentile · Typescript · large (100-500K LoC) Scanner says 67 (higher by 19)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 5 days ago · v7 · 257 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 85.0 0.15 12.75
security_score 96.0 0.25 24.00
testing_score 100.0 0.20 20.00
documentation_score 89.0 0.15 13.35
practices_score 69.0 0.15 10.35
code_quality 50.7 0.10 5.07
Overall 1.00 85.5
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
Dangling fetch: POST http://localhost:3000 (examples/stream-to-client-raw.ts:21)
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.
#2
Dangling fetch: POST http://localhost:3000 (examples/stream-to-client-browser.ts:13)
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.
#3
Dangling fetch: POST http://localhost:3000 (examples/stream-to-client-next.ts:17)
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.
#4
Dangling fetch: POST http://localhost:3000 (examples/stream-to-client-express.ts:21)
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
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish-jsr.yml
#6
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/create-releases.yml
#7
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish-npm.yml
#8
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/ci.yml
#9
`fetch()` without try/.catch or AbortSignal — examples/stream-to-client-browser.ts:13
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in examples/stream-to-client-browser.ts:13, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#10
`fetch()` without try/.catch or AbortSignal — examples/stream-to-client-next.ts:17
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in examples/stream-to-client-next.ts:17, 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.

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/e4d4c80f-102b-4c6f-b2fd-1a5fa991e3a4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e4d4c80f-102b-4c6f-b2fd-1a5fa991e3a4/

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.