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

Furnace-Chronicles/Emerald-Summit

https://github.com/Furnace-Chronicles/Emerald-Summit · scanned 2026-06-17 01:27 UTC (1 month, 2 weeks ago)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · 0 actionable findings from 0 signal sources. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
76.7
/100
Security checks
77
0 findings
System graph
77
11.1% cov · 0 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 0 Low 0 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 0 Crowd 0

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

v1
Jun 16 04:23
v2
Jun 17 01:27
Diff: previous → latest scan
Score Δ
0.00
Gaps added
0
Gaps resolved
0
Edges changed
+0 / -0
v#IDStatusScoreGapsNodesCommitStarted
v scan_0b6abf46828d ok 76.7 — 1 — Jun 17 01:27
v scan_034f54b6af24 ok 76.7 — 1 — Jun 16 04:23
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/ec184cc0-4c77-4cf5-9a34-eb825c4fb2f2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ec184cc0-4c77-4cf5-9a34-eb825c4fb2f2/

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.