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

aquasecurity/vuln-list

https://github.com/aquasecurity/vuln-list · scanned 2026-06-05 20:39 UTC (4 days, 13 hours ago) · 10 languages

2 findings 11/13 scanners ran 45th percentile · Unknown ·

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

Complete repo analysis

2 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

Combined
71.7
/100
Security checks
72
2 findings
System graph
—
—% cov · 0 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 45.0 0.15 6.75
security_score 100.0 0.25 25.00
testing_score 70.0 0.20 14.00
documentation_score 40.0 0.15 6.00
practices_score 70.0 0.15 10.50
code_quality 80.0 0.10 8.00
Overall 1.00 70.2
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 0 High 0 Medium 1 Low 1 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 2 System graph 0 Crowd 0 Layer: Quality 2
No flows synthesized yet.
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/0da9b40a-afe0-4745-9575-8f5b86758d3f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0da9b40a-afe0-4745-9575-8f5b86758d3f/

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.