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 6.0s · analysis 6.79s · 16.5 MB · GitHub API rate-limit (preflight)

vitejs/vite

https://github.com/vitejs/vite · scanned 2026-05-31 01:26 UTC (5 days, 8 hours ago) · 10 languages

658 findings (90 legacy + 568 scanner) 67th percentile · Javascript · medium (20-100K LoC) Scanner says 61 (higher by 17)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 8 hours ago · v2 · last Δ +5.4 (diff) · 364 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 76.0 0.25 19.00
testing_score 95.0 0.20 19.00
documentation_score 76.1 0.15 11.41
practices_score 88.0 0.15 13.20
code_quality 58.5 0.10 5.85
Overall 1.00 77.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
.env file present in repo: playground/assets-sanitize/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#2
.env file present in repo: playground/html/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#3
.env file present in repo: playground/env-nested/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#4
.env file present in repo: playground/fs-serve/root/src/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#5
Insecure pattern 'exec_used' in packages/vite/src/node/server/openBrowser.ts:141
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/vite/src/node/server/openBrowser.ts:141
#6
Insecure pattern 'exec_used' in packages/create-vite/src/index.ts:872
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
packages/create-vite/src/index.ts:872
#7
Dangling fetch: GET /assets/${name}.js (playground/legacy/immutable-chunk.js:14)
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 /ping (playground/optimize-deps/glob/foo.js:3)
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
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#10
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/copilot-setup-steps.yml

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/ce0b060e-269d-4cad-aeaf-986153a5541a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ce0b060e-269d-4cad-aeaf-986153a5541a/

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.