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

zimdin12/aify-comms

https://github.com/zimdin12/aify-comms · scanned 2026-06-16 01:13 UTC (2 months, 1 week ago)

392 raw signals (0 security + 392 graph)

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

Complete repo analysis

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

JSON
Combined
68.7
/100
Security checks
69
0 findings
System graph
69
100.0% cov · 389 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 7 Medium 24 Low 218 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 389 Crowd 0 Layer: Software 14 Frontend 77 Network 1 Hardware 3 Security 19 Cicd 1 Quality 224 Api 50

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

v1
Jun 16 01:12
v#IDStatusScoreGapsNodesCommitStarted
v scan_abebac25a5d2 ok 68.7 392 3422 8a7f639 dirty Jun 16 01:12
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/25475275-3077-4a75-8bed-aac1bb34957f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/25475275-3077-4a75-8bed-aac1bb34957f/

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.