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

RSNxru/essenz-master-orchestrator

https://github.com/RSNxru/essenz-master-orchestrator · scanned 2026-06-15 23:56 UTC (2 months, 3 weeks ago)

9 raw signals (0 security + 9 graph)

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

Complete repo analysis

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

JSON
Combined
91.3
/100
Security checks
91
0 findings
System graph
91
88.9% cov · 9 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 3 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 9 Crowd 0 Layer: Hardware 3 Frontend 1 Security 1 Cicd 1 Quality 3

All 41 nodes from the latest scan, grouped by kind. Each node is a unit the engine identified (file, function, endpoint, table…). Most users won't need this view — it's primarily for debugging the engine's graph extraction or for AI agents that want to enumerate the project structure.

LabelLayerStatusPath
image::gateway/Dockerfile hardware healthy gateway/Dockerfile
gateway hardware healthy docker-compose.yml
portal_web hardware healthy docker-compose.yml
inshop_web hardware healthy docker-compose.yml
auth_db hardware healthy docker-compose.yml
auth_web hardware healthy docker-compose.yml
notifications_redis hardware healthy docker-compose.yml
notifications_web hardware healthy docker-compose.yml
notifications_worker hardware healthy docker-compose.yml
n8n hardware healthy docker-compose.yml
events_db hardware healthy docker-compose.yml
events_redis hardware healthy docker-compose.yml
events_web hardware healthy docker-compose.yml
events_worker hardware healthy docker-compose.yml

LabelLayerStatusPath
port:8080 network healthy docker-compose.yml
port:80 network healthy docker-compose.yml
port:5432 network healthy docker-compose.yml
port:8000 network healthy docker-compose.yml
port:6379 network healthy docker-compose.yml
port:8001 network healthy docker-compose.yml
port:5678 network healthy docker-compose.yml
port:5433 network healthy docker-compose.yml
port:6380 network healthy docker-compose.yml
port:8002 network healthy docker-compose.yml

LabelLayerStatusPath
README.md software healthy README.md
.env.example software healthy .env.example
docker-compose.yml software healthy docker-compose.yml
04-operaciones.md software healthy docs/04-operaciones.md
README.md software healthy docs/README.md
03-red-y-variables.md software healthy docs/03-red-y-variables.md
01-arquitectura.md software healthy docs/01-arquitectura.md
02-gateway.md software healthy docs/02-gateway.md
Dockerfile software healthy gateway/Dockerfile

LabelLayerStatusPath
postgresql data healthy README.md
redis data healthy README.md
postgres data healthy docker-compose.yml

LabelLayerStatusPath
docs software healthy docs
gateway software healthy gateway

LabelLayerStatusPath
repobility-clone-wtk96scx software healthy /tmp/repobility-clone-wtk96scx

LabelLayerStatusPath
celery data healthy README.md

LabelLayerStatusPath
nginx network healthy README.md
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/dae58ac7-5e0a-4c8c-aacd-c3bb34bbcbe3/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/dae58ac7-5e0a-4c8c-aacd-c3bb34bbcbe3/

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.