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

redis/RedisInsight

https://github.com/redis/RedisInsight · scanned 2026-06-15 23:50 UTC (2 months, 3 weeks ago)

482 raw signals (0 security + 482 graph)

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

Complete repo analysis

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

JSON
Combined
53.0
/100
Security checks
53
0 findings
System graph
53
100.0% cov · 400 findings
Critical
27
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 27 High 13 Medium 58 Low 107 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 400 Crowd 0 Layer: Frontend 181 Network 13 Hardware 40 Security 50 Cicd 6 Quality 60 Api 50

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

v1
Jun 15 23:50
v#IDStatusScoreGapsNodesCommitStarted
v scan_d36e358a6bfd ok 53.0 482 17146 80527c5 Jun 15 23:50
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/5cb3c917-74a9-4ce1-9ace-c047ab999a25/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5cb3c917-74a9-4ce1-9ace-c047ab999a25/

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.