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

sybil-solutions/vllm-studio

https://github.com/sybil-solutions/vllm-studio · scanned 2026-06-16 00:27 UTC (2 months, 2 weeks ago)

244 raw signals (0 security + 244 graph)

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

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 238 actionable findings from 1 signal source. 6 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
41.3
/100
Security checks
41
0 findings
System graph
41
100.0% cov · 238 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 84 Medium 54 Low 24 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 238 Crowd 0 Layer: Frontend 52 Network 1 Hardware 4 Security 19 Cicd 3 Quality 67 Api 92

Last 1 scan of this repo. Each new scan persists a full payload — historical comparison is exact, not lossy.

v1
Jun 16 00:27
v#IDStatusScoreGapsNodesCommitStarted
v scan_5ec453d1d714 ok 41.3 244 3925 ce9e278 v1.48.1 Jun 16 00:27
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/0ad7f039-d45b-480f-8d71-977c7fc958fe/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0ad7f039-d45b-480f-8d71-977c7fc958fe/

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.