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.

pi-apps/pi-explorer

https://github.com/pi-apps/pi-explorer · scanned 2026-08-17 03:34 UTC (3 weeks, 4 days ago)

127 raw signals (0 security + 127 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 weeks, 4 days ago · v1 · 118 actionable findings from 1 signal source. 9 repeated signals grouped for readability. 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: source: legacy × excluding tests × Reset all
Scan summary Repository scanned at 78.7/100 with 80.0% coverage. It contains 418 nodes across 20 cross-layer flows, written primarily in mixed languages. Engine surfaced 127 findings — concentrated in security (81), dependencies (24), quality (13). Risk profile is high: 3 critical, 29 high, 71 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 0 of 118 actionable findings. 127 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

No findings match the active filters. Reset →
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/7761f1b5-e2c9-429e-ab22-8dea5f52ef43/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7761f1b5-e2c9-429e-ab22-8dea5f52ef43/

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.