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

zyx1121/kilo-sense

https://github.com/zyx1121/kilo-sense · scanned 2026-06-16 01:13 UTC (2 months, 1 week ago)

43 raw signals (34 security + 9 graph)

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

Complete repo analysis

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

JSON
Combined
94.9
/100
Security checks
95
7 findings
System graph
95
66.7% cov · 9 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 3 Medium 7 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 9 Crowd 0 Layer: Quality 13 Security 2 Frontend 1

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

v1
Jun 16 01:13
v#IDStatusScoreGapsNodesCommitStarted
v scan_61d51173149c ok 94.9 9 65 db99e92 v0.2.0 Jun 16 01:13
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/b55e04b7-e807-4862-bbd5-87e3c8e8799c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b55e04b7-e807-4862-bbd5-87e3c8e8799c/

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.