← Back to scan
File as GitHub Issue repo: dockur/windows

Push this scan report to dockur/windows

Click 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.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Action `actions/checkout` pinned to mutable ref `@v6`

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… src/define.sh:1522
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… src/define.sh:1512
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… src/define.sh:1509
HIGH MINED115 Action `peter-evans/dockerhub-description` pinned to mutable ref `@v5` .github/workflows/hub.yml:20
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v6` .github/workflows/hub.yml:17
HIGH MINED115 Action `action-pack/send-mail` pinned to mutable ref `@v1` .github/workflows/build.yml:94
HIGH MINED115 Action `action-pack/gitlab-sync` pinned to mutable ref `@v3` .github/workflows/build.yml:87
HIGH MINED115 Action `action-pack/bump` pinned to mutable ref `@v2` .github/workflows/build.yml:82
HIGH MINED115 Action `action-pack/github-release` pinned to mutable ref `@v2` .github/workflows/build.yml:75
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v6` .github/workflows/build.yml:25
HIGH MINED115 Action `GrantBirki/json-yaml-validate` pinned to mutable ref `@v5.0.0` .github/workflows/check.yml:33
HIGH MINED115 Action `action-pack/valid-xml` pinned to mutable ref `@v1` .github/workflows/check.yml:27
HIGH MINED115 Action `hadolint/hadolint-action` pinned to mutable ref `@v3.3.0` .github/workflows/check.yml:20
HIGH MINED115 Action `ludeeus/action-shellcheck` pinned to mutable ref `@master` .github/workflows/check.yml:15
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v6` .github/workflows/check.yml:12
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v6` .github/workflows/links.yml:21
HIGH MINED115 Action `reviewdog/action-shellcheck` pinned to mutable ref `@v1` .github/workflows/review.yml:66
HIGH MINED115 Action `reviewdog/action-shfmt` pinned to mutable ref `@v1` .github/workflows/review.yml:57
HIGH MINED115 Action `reviewdog/action-actionlint` pinned to mutable ref `@v1` .github/workflows/review.yml:50
HIGH MINED115 Action `reviewdog/action-yamllint` pinned to mutable ref `@v1` .github/workflows/review.yml:42
HIGH MINED115 Action `reviewdog/action-hadolint` pinned to mutable ref `@v1` .github/workflows/review.yml:33
HIGH MINED115 Action `reviewdog/action-misspell` pinned to mutable ref `@v1` .github/workflows/review.yml:21
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v6` .github/workflows/review.yml:18
HIGH MINED118 Dockerfile FROM `dockurr/windows-arm (no tag)` not pinned by digest Dockerfile:34
MED DKR002 Compose service `windows` image has no explicit tag compose.yml:1
MED DKR009 Dockerfile separates apt update from install Dockerfile:16
MED DKR013 Dockerfile ADD downloads remote content Dockerfile:33
MED DKR001 Docker final stage has no non-root USER Dockerfile:36
MED DKC005 Compose service adds dangerous Linux capabilities compose.yml:1
LOW DKR008 .dockerignore misses sensitive defaults .dockerignore
LOW DKC010 Compose service lacks no-new-privileges hardening compose.yml:1
LOW DKC006 Compose service does not declare a runtime user compose.yml:1
Reset to top 5 32 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `dockur/windows`

**Score: 71/100 (B-)**  ·  32 findings  ·  scanned 2026-06-05 11:33 UTC  ·  0 LOC

| Severity | Count |
|---|---|
| CRITICAL | 3 |
| HIGH | 21 |
| MEDIUM | 5 |
| LOW | 3 |

📊 [Full filterable report](https://repobility.com/scan/1dc2cb3e-e8f7-498f-bcd7-abe76849e999/)  ·  ![scorecard](https://repobility.com/scan/1dc2cb3e-e8f7-498f-bcd7-abe76849e999/report.png?v=1780659214-s2)

### Top findings

1. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive 
   `src/define.sh:1522`
2. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive 
   `src/define.sh:1512`
3. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive 
   `src/define.sh:1509`
4. **HIGH** `MINED115` — Action `peter-evans/dockerhub-description` pinned to mutable ref `@v5`
   `.github/workflows/hub.yml:20` · ✓ Repobility
5. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v6`
   `.github/workflows/hub.yml:17` · ✓ Repobility

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/1dc2cb3e-e8f7-498f-bcd7-abe76849e999/_
Megaproject â high spam risk
Could not determine 'dockur/windows' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
Already filed
20/35 findings (57%) on this scan are already flagged as test-file, won't-fix, or suppressed. The scan is too noisy to file as a single issue. Curate down to specific actionable findings, or address the FP source first.
Open in GitHub to file this issue Filing guard overridden Cancel

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.