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 5.43s · analysis 1.23s · 7.1 MB · GitHub API rate-limit (preflight)

gdluxx/gdluxx

https://github.com/gdluxx/gdluxx · scanned 2026-05-26 08:24 UTC (1 week, 3 days ago) · 10 languages

238 findings (70 legacy + 168 scanner) 29th percentile · Typescript · medium (20-100K LoC) Scanner says 81 (lower by 20)

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

Complete repo analysis

Last scanned 1 week, 3 days ago · v2 · 154 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
78.0
/100
Repobility
75
70 legacy
9-layer
81
100.0% cov · 84 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 79.8 0.25 19.95
testing_score 0.0 0.20 0.00
documentation_score 68.7 0.15 10.30
practices_score 77.0 0.15 11.55
code_quality 61.3 0.10 6.13
Overall 1.00 60.7
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 50 Medium 21 Low 73 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 70 9-layer 84 Crowd 0 Layer: Quality 46 Cicd 27 Security 4 Software 70 Api 1 Frontend 2 Network 1 Hardware 3

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

#1
Privileged port 1000 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in Dockerfile is a real port, change the binding to ≥1024 or run behind a proxy.
Dockerfile
#2
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/docs.yml
#3
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml:27
#4
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml:34
#5
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml:63
#6
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml:67
#7
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml:76
#8
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml:88
#9
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml
#10
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/extension-release.yml:24

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/5e6580f3-145e-402c-a28f-72aff412ab0b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5e6580f3-145e-402c-a28f-72aff412ab0b/

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.