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.
Sign up free Scan another repo

ThomasJohnson-Botanyze/satisfactory-flow-calculator

https://github.com/ThomasJohnson-Botanyze/satisfactory-flow-calculator · scanned 2026-06-16 00:35 UTC (2 months, 2 weeks ago)

43 raw signals (1 security + 42 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 43 actionable findings from 2 signal sources. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
98.6
/100
Security checks
99
1 findings
System graph
99
66.7% cov · 42 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 8 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 1 System graph 42 Crowd 0 Layer: Quality 28 Frontend 12 Security 2 Cicd 1

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

v1
Jun 16 00:35
v#IDStatusScoreGapsNodesCommitStarted
v scan_376811682d52 ok 98.6 42 664 15c1e04 v2.15.2 Jun 16 00:35
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/be2e95c1-f445-461f-a4da-858d398c7052/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/be2e95c1-f445-461f-a4da-858d398c7052/

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.