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.

Zipstack/unstract

https://github.com/Zipstack/unstract · scanned 2026-06-16 04:42 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 · v1 · 0 actionable findings from 0 signal sources. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

55.6% cov · 0 findings

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

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 100.0/100 with 55.6% coverage. It contains 25 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 0 findings. Risk profile is low: 0 critical, 0 high, 0 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 0 of 0 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

No findings yet. Click "Run all analyses" to begin.

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/e48a83fb-657f-4dc2-8f2c-27084e426e9c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e48a83fb-657f-4dc2-8f2c-27084e426e9c/

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.