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

Scan timing: clone 1.5s · analysis 1.28s · 0.5 MB · GitHub API rate-limit (preflight)

alireza0/s-ui

https://github.com/alireza0/s-ui.git · scanned 2026-05-21 16:00 UTC (2 weeks ago) · 10 languages

178 findings (86 legacy + 92 scanner) 0th percentile · Go · small (2-20K LoC) Scanner says 67 (lower by 3)

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

Complete repo analysis

Last scanned 2 weeks ago · v2 · 132 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
73.3
/100
Repobility
79
86 legacy
9-layer
67
100.0% cov · 46 gaps
Critical
3
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 73.4 0.25 18.35
testing_score 0.0 0.20 0.00
documentation_score 75.0 0.15 11.25
practices_score 79.0 0.15 11.85
code_quality 75.3 0.10 7.53
Overall 1.00 64.0
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 51 Medium 22 Low 34 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 86 9-layer 46 Crowd 0 Layer: Security 19 Cicd 45 Quality 30 Software 31 Api 1 Hardware 5 Frontend 1

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in install.sh
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in install.sh:92; move to env var / secrets manager.
install.sh:92
#2
Possible secret in s-ui.sh
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in s-ui.sh:146; move to env var / secrets manager.
s-ui.sh:146
#3
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#4
Docker base image uses a mutable or implicit tag: alpine
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
Dockerfile:40
#5
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:57
#6
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:67
#7
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:69
#8
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:78
#9
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:83
#10
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docker.yml:90

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/62091803-8d8b-4db5-9ad7-1008fd52865a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/62091803-8d8b-4db5-9ad7-1008fd52865a/

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.