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.63s · analysis 10.16s · 27.9 MB · GitHub API rate-limit (preflight)

astral-sh/uv

https://github.com/astral-sh/uv · scanned 2026-05-31 01:25 UTC (5 days, 14 hours ago) · 10 languages

493 findings (142 legacy + 351 scanner) 11/13 scanners ran 67th percentile · Rust · huge (>500K LoC) Scanner says 73 (higher by 11)

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

Complete repo analysis

Last scanned 5 days, 14 hours ago · v2 · 320 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
77.4
/100
Repobility
81
142 legacy
9-layer
73
100.0% cov · 178 gaps
Critical
37
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 84.0 0.20 16.80
documentation_score 100.0 0.15 15.00
practices_score 100.0 0.15 15.00
code_quality 35.0 0.10 3.50
Overall 1.00 84.3
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 37 High 94 Medium 27 Low 128 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 142 9-layer 178 Crowd 0 Layer: Quality 222 Software 51 Cicd 10 Security 30 Api 1 Network 2 Hardware 3 Frontend 1

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

#1
Possible secret in crates/uv-client/src/registry_client.rs
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 crates/uv-client/src/registry_client.rs:1739; move to env var / secrets manager.
crates/uv-client/src/registry_client.rs:1739
#2
Possible secret in crates/uv-client/src/registry_client.rs
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 crates/uv-client/src/registry_client.rs:1795; move to env var / secrets manager.
crates/uv-client/src/registry_client.rs:1795
#3
Possible secret in crates/uv-client/src/registry_client.rs
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 crates/uv-client/src/registry_client.rs:1845; move to env var / secrets manager.
crates/uv-client/src/registry_client.rs:1845
#4
Possible secret in crates/uv-auth/src/middleware.rs
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 crates/uv-auth/src/middleware.rs:1048; move to env var / secrets manager.
crates/uv-auth/src/middleware.rs:1048
#5
Possible secret in crates/uv-auth/src/middleware.rs
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 crates/uv-auth/src/middleware.rs:1094; move to env var / secrets manager.
crates/uv-auth/src/middleware.rs:1094
#6
Possible secret in crates/uv-auth/src/middleware.rs
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 crates/uv-auth/src/middleware.rs:1208; move to env var / secrets manager.
crates/uv-auth/src/middleware.rs:1208
#7
Possible secret in crates/uv-auth/src/middleware.rs
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 crates/uv-auth/src/middleware.rs:1249; move to env var / secrets manager.
crates/uv-auth/src/middleware.rs:1249
#8
Possible secret in crates/uv-auth/src/middleware.rs
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 crates/uv-auth/src/middleware.rs:1297; move to env var / secrets manager.
crates/uv-auth/src/middleware.rs:1297
#9
Possible secret in crates/uv-auth/src/middleware.rs
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 crates/uv-auth/src/middleware.rs:1337; move to env var / secrets manager.
crates/uv-auth/src/middleware.rs:1337
#10
Possible secret in crates/uv-auth/src/middleware.rs
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 crates/uv-auth/src/middleware.rs:1380; move to env var / secrets manager.
crates/uv-auth/src/middleware.rs:1380

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/bee51646-a8dc-410c-9ffa-753bd32e1390/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/bee51646-a8dc-410c-9ffa-753bd32e1390/

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.