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

wombow-ai/tickwind

https://github.com/wombow-ai/tickwind · scanned 2026-06-16 00:59 UTC (2 months, 1 week ago)

72 raw signals (5 security + 67 graph)

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

Complete repo analysis

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

JSON
Combined
53.6
/100
Security checks
54
3 findings
System graph
54
100.0% cov · 67 findings
Critical
0
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 0 High 2 Medium 38 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 3 System graph 67 Crowd 0 Layer: Quality 30 Api 1 Frontend 19 Hardware 4 Security 14 Cicd 2

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

v1
Jun 16 00:59
v#IDStatusScoreGapsNodesCommitStarted
v scan_02723d8e820b ok 53.6 67 1271 b44de40 Jun 16 00:59
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/1c6cc8ed-d8b0-4eac-8204-056411475614/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1c6cc8ed-d8b0-4eac-8204-056411475614/

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.