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.

digitie/pinvi

https://github.com/digitie/pinvi · scanned 2026-06-17 01:56 UTC (1 month, 1 week ago)

201 raw signals (0 security + 201 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -31.3 (diff) · 178 actionable findings from 1 signal source. 23 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: excluding tests × Reset all

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

v1
Jun 16 03:57
v2
Jun 17 01:56
Diff: previous → latest scan
Score Δ
-31.30
Gaps added
199
Gaps resolved
0
Edges changed
+3975 / -0
New gaps in latest scan:
  • Possibly dead Python function: list_change_requests low
  • Possibly dead Python function: reject_change_request low
  • Possibly dead Python function: default_mcp_scopes low
  • Possibly dead Python function: dependency low
  • Possibly dead Python function: require_mcp_read low
  • + 194 more
v#IDStatusScoreGapsNodesCommitStarted
v scan_ed48b4dc9c1e ok 45.4 201 3005 Jun 17 01:56
v scan_35acd5adb96c ok 76.7 1 Jun 16 03:57
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/dbf96fc3-c12d-44ce-ae66-e01031268471/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/dbf96fc3-c12d-44ce-ae66-e01031268471/

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.