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
47 of your 177 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

vercel/next.js

https://github.com/vercel/next.js.git · scanned 2026-05-18 14:32 UTC (2 weeks, 4 days ago) · 10 languages

19517 findings (177 legacy + 19340 scanner) 8/10 scanners ran 38th percentile · Typescript · huge (>500K LoC) Scanner says 71 (higher by 11)

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

Complete repo analysis

Last scanned 2 weeks, 4 days ago · v6 · 3391 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
75.9
/100
Repobility
81
177 legacy
9-layer
71
100.0% cov · 3214 gaps
Critical
3
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 100.0 0.25 25.00
testing_score 95.0 0.20 19.00
documentation_score 63.0 0.15 9.45
practices_score 76.0 0.15 11.40
code_quality 80.0 0.10 8.00
Overall 1.00 81.8
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
Severity: Critical 3 High 127 Medium 884 Low 1413 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 177 9-layer 3214 Crowd 0 Layer: Quality 1307 Security 105 Cicd 47 Software 57 Frontend 1860 Network 2 Hardware 13

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

#1
Possible secret in packages/next/src/compiled/node-html-parser/index.js
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/next/src/compiled/node-html-parser/index.js:1; move to env var / secrets manager.
packages/next/src/compiled/node-html-parser/index.js:1
#2
Insecure pattern 'eval_used' in turbopack/crates/turbopack-ecmascript/src/webpack/parse.rs:152
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
turbopack/crates/turbopack-ecmascript/src/webpack/parse.rs:152
#3
Insecure pattern 'eval_used' in turbopack/crates/turbopack-ecmascript/src/analyzer/graph.rs:412
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
turbopack/crates/turbopack-ecmascript/src/analyzer/graph.rs:412
#4
Insecure pattern 'exec_used' in turbopack/crates/turbopack-ecmascript-runtime/js/src/nodejs/runtime/dev-base.ts:69
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
turbopack/crates/turbopack-ecmascript-runtime/js/src/nodejs/runtime/dev-base.ts:69
#5
Insecure pattern 'eval_used' in turbopack/crates/turbopack-ecmascript-runtime/js/src/browser/runtime/dom/dev-backend-dom.ts:144
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
turbopack/crates/turbopack-ecmascript-runtime/js/src/browser/runtime/dom/dev-backend-dom.ts:144
#6
Insecure pattern 'exec_used' in scripts/pack-next.ts:82
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/pack-next.ts:82
#7
Insecure pattern 'exec_used' in scripts/automated-update-workflow.js:53
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/automated-update-workflow.js:53
#8
Insecure pattern 'exec_used' in scripts/unpack-next.ts:29
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/unpack-next.ts:29
#9
Insecure pattern 'exec_used' in scripts/patch-next.ts:141
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/patch-next.ts:141
#10
Insecure pattern 'eval_used' in crates/next-core/src/segment_config.rs:623
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
crates/next-core/src/segment_config.rs:623

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/c62673f3-12b0-4330-8614-ead9a08d2948/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c62673f3-12b0-4330-8614-ead9a08d2948/

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.