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.

seankim2/virtual_acp

https://github.com/seankim2/virtual_acp · scanned 2026-06-16 04:38 UTC (1 month, 3 weeks ago)

3 raw signals (0 security + 3 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 3 weeks ago · v1 · 3 actionable findings 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 7 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
.env.example software healthy .env.example
package-lock.json software healthy package-lock.json
README.md software healthy README.md
package.json software healthy package.json
virtuals_eval_issue_report_2026-02-28.md software healthy virtuals_eval_issue_report_2026-02-28.md
ecosystem.config.cjs software healthy ecosystem.config.cjs

LabelLayerStatusPath
seankim2__virtual_acp software healthy /data/fable5_failed_archive/seankim2__virtual_acp
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/a7d06d4d-3f93-4da0-92de-13fe3542c794/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a7d06d4d-3f93-4da0-92de-13fe3542c794/

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.