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.

unbreached/CGTerm-3.0

https://github.com/unbreached/CGTerm-3.0 · scanned 2026-06-16 04:40 UTC (1 month, 3 weeks ago)

1 raw signals (0 security + 1 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 3 weeks ago · v1 · 1 actionable finding from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

All 8 nodes from the latest scan, grouped by kind. Each node is a unit the engine identified (file, function, endpoint, table…). Most users won't need this view — it's primarily for debugging the engine's graph extraction or for AI agents that want to enumerate the project structure.

LabelLayerStatusPath
MUSIC-IMPLEMENTATION.md software healthy MUSIC-IMPLEMENTATION.md
README software healthy README
CHANGELOG.md software healthy CHANGELOG.md
SECURITY-FIXES-APPLIED.md software healthy SECURITY-FIXES-APPLIED.md
Makefile software healthy Makefile
README.txt software healthy README.txt
LICENSE software healthy LICENSE

LabelLayerStatusPath
unbreached__CGTerm-3.0 software healthy /data/fable5_failed_archive/unbreached__CGTerm-3.0
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/e36e76a7-081e-48f5-b100-d3f1d2463ba2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e36e76a7-081e-48f5-b100-d3f1d2463ba2/

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.