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

trinity-aml/TorrServer-LT

https://github.com/trinity-aml/TorrServer-LT · scanned 2026-06-16 00:41 UTC (2 months, 1 week ago)

49 raw signals (0 security + 49 graph)

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

Complete repo analysis

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

JSON
Combined
57.0
/100
Security checks
57
0 findings
System graph
57
88.9% cov · 38 findings
Critical
2
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 2 High 1 Medium 23 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 38 Crowd 0 Layer: Frontend 2 Hardware 10 Security 6 Cicd 3 Quality 15 Api 2

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

v1
Jun 16 00:41
v#IDStatusScoreGapsNodesCommitStarted
v scan_8fcfdc1afee0 ok 57.0 49 933 83600fa MatriX.141.LT-001 Jun 16 00:41
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/e3f40a11-7857-4da8-97d7-b7e43cecccf2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e3f40a11-7857-4da8-97d7-b7e43cecccf2/

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.