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

volcengine/OpenViking

https://github.com/volcengine/OpenViking.git · scanned 2026-05-16 08:27 UTC (2 weeks, 6 days ago) · 10 languages

556 findings (121 legacy + 435 scanner) 15th percentile · Python · large (100-500K LoC) Scanner says 55 (higher by 6)

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

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 113 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
51.8
/100
Repobility
49
113 legacy
9-layer
55
100.0% cov · 0 gaps
Critical
5
click to filter
Agents
6
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 5 High 82 Medium 11 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 113 9-layer 0 Crowd 0 Layer: Quality 22 Security 49 Cicd 36 Software 6

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

v1
May 16 08:27
v#IDStatusScoreGapsNodesCommitStarted
v scan_23176e424136 ok 55.1 435 17761 af4c54f May 16 08: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/12056a6a-d5b1-4a95-9bc1-27d844e39785/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/12056a6a-d5b1-4a95-9bc1-27d844e39785/

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.