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

team-attention/tide

https://github.com/team-attention/tide · scanned 2026-06-16 00:31 UTC (2 months, 2 weeks ago)

379 raw signals (0 security + 379 graph)

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

Complete repo analysis

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

JSON
Combined
57.8
/100
Security checks
58
0 findings
System graph
58
100.0% cov · 373 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 0 Medium 74 Low 150 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 373 Crowd 0 Layer: Api 1 Frontend 12 Security 63 Cicd 4 Quality 293

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

v1
Jun 16 00:31
v#IDStatusScoreGapsNodesCommitStarted
v scan_c0e5e93a3487 ok 57.8 379 3215 11d8bd5 tide-v0.1.57 Jun 16 00:31
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/296c99c2-6f88-4c86-9469-267dc357150a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/296c99c2-6f88-4c86-9469-267dc357150a/

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.