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

juyterman1000/entroly

https://github.com/juyterman1000/entroly.git · scanned 2026-05-16 08:41 UTC (2 weeks, 6 days ago) · 10 languages

264 findings (68 legacy + 196 scanner) 20th percentile · Python · large (100-500K LoC) Scanner says 70 (lower by 7)

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

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 49 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
62.3
/100
Repobility
54
49 legacy
9-layer
71
100.0% cov · 0 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 24 Medium 11 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 49 9-layer 0 Crowd 0 Layer: Cicd 8 Quality 21 Security 19 Software 1

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

v1
May 16 08:41
v#IDStatusScoreGapsNodesCommitStarted
v scan_8f2fa86a5f75 ok 70.5 196 3871 f432f5c May 16 08:41
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/2e056297-f8d0-4ae0-ad1d-c05b27731c71/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2e056297-f8d0-4ae0-ad1d-c05b27731c71/

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.