Yenthe666/InstallScript
Yenthe666/InstallScriptClick the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Compose service does not declare a runtime user
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `Yenthe666/InstallScript` **Score: 73/100 (B)** · 4 findings · scanned 2026-05-18 01:46 UTC · 0 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 0 | | MEDIUM | 2 | | LOW | 2 | 📊 [Full filterable report](https://repobility.com/scan/c0b67f92-6a20-4f1a-aaad-c24f8255530c/) ·  ### Top findings 1. **MEDIUM** `DKR007` — Docker build context has no .dockerignore `.dockerignore` 2. **MEDIUM** `DKR001` — Docker final stage has no non-root USER `test_install/Dockerfile:1` 3. **LOW** `DKC010` — Compose service lacks no-new-privileges hardening `test_install/docker-compose.yml:1` 4. **LOW** `DKC006` — Compose service does not declare a runtime user `test_install/docker-compose.yml:1` --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/c0b67f92-6a20-4f1a-aaad-c24f8255530c/_
The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.