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

vrushabh-rajaghatta/ligature

https://github.com/vrushabh-rajaghatta/ligature · scanned 2026-06-16 00:53 UTC (2 months, 1 week ago)

907 raw signals (0 security + 907 graph)

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

Complete repo analysis

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

JSON
Combined
57.4
/100
Security checks
57
0 findings
System graph
57
100.0% cov · 899 findings
Critical
1
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 1 High 198 Medium 78 Low 146 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 899 Crowd 0 Layer: Software 5 Frontend 248 Security 56 Cicd 1 Quality 380 Api 209

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

v1
Jun 16 00:53
v#IDStatusScoreGapsNodesCommitStarted
v scan_bf7902a3d224 ok 57.4 907 9254 6c59f0e Jun 16 00:53
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/35727940-1801-4dbb-9d82-532b3a262079/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/35727940-1801-4dbb-9d82-532b3a262079/

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.