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.

JP401cmd/fin-first

https://github.com/JP401cmd/fin-first · scanned 2026-06-16 02:54 UTC (2 months, 1 week ago)

51 raw signals (24 security + 27 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v2 · 35 actionable findings from 2 signal sources. 61 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 27 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 4 Medium 14 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 27 Crowd 0 Layer: Quality 15 Security 9 Frontend 8 Hardware 1 Cicd 2

Exclude dismissed / FP Exclude test files

No flows synthesized yet.

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/d8615396-3733-4c01-b3c8-01a9fe952fe3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d8615396-3733-4c01-b3c8-01a9fe952fe3/

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.