← Back to scan
File as GitHub Issue repo: redpanda-data/kminion

Push this scan report to redpanda-data/kminion

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
HIGH MINED016 [MINED016] Go Error Ignored: _, err := fn() with err not checked. Go anti-pattern. minion/offset_consumer.go:30
HIGH DKR014 Dockerfile copies the entire context without .dockerignore Dockerfile:18
HIGH MINED115 Action `goreleaser/goreleaser-action` pinned to mutable ref `@v7` .github/workflows/goreleaser.yml:18
HIGH MINED115 Action `actions/setup-go` pinned to mutable ref `@v6` .github/workflows/goreleaser.yml:15
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v6` .github/workflows/goreleaser.yml:12
HIGH MINED115 Action `aws-actions/amazon-ecr-login` pinned to mutable ref `@v2` .github/workflows/docker-image.yml:56
HIGH MINED115 Action `aws-actions/configure-aws-credentials` pinned to mutable ref `@v4` .github/workflows/docker-image.yml:51
HIGH MINED115 Action `actions/checkout` pinned to mutable ref `@v4` .github/workflows/docker-image.yml:24
HIGH MINED115 Action `aws-actions/aws-secretsmanager-get-secrets` pinned to mutable ref `@v2` .github/workflows/docker-image.yml:19
HIGH MINED115 Action `aws-actions/configure-aws-credentials` pinned to mutable ref `@v4` .github/workflows/docker-image.yml:15
HIGH MINED118 Dockerfile FROM `alpine:3` not pinned by digest Dockerfile:30
HIGH MINED118 Dockerfile FROM `golang:1.26.3-alpine` not pinned by digest Dockerfile:4
HIGH GO-2026-5039 stdlib: GO-2026-5039 go.mod
HIGH GO-2026-5038 stdlib: GO-2026-5038 go.mod
HIGH GO-2026-5037 stdlib: GO-2026-5037 go.mod
HIGH GO-2026-5033 golang.org/x/crypto: GO-2026-5033 go.mod
HIGH GO-2026-5023 golang.org/x/crypto: GO-2026-5023 go.mod
HIGH GO-2026-5021 golang.org/x/crypto: GO-2026-5021 go.mod
HIGH GO-2026-5020 golang.org/x/crypto: GO-2026-5020 go.mod
HIGH GO-2026-5019 golang.org/x/crypto: GO-2026-5019 go.mod
HIGH GO-2026-5018 golang.org/x/crypto: GO-2026-5018 go.mod
HIGH GO-2026-5017 golang.org/x/crypto: GO-2026-5017 go.mod
HIGH GO-2026-5016 golang.org/x/crypto: GO-2026-5016 go.mod
HIGH GO-2026-5015 golang.org/x/crypto: GO-2026-5015 go.mod
HIGH GO-2026-5014 golang.org/x/crypto: GO-2026-5014 go.mod
HIGH GO-2026-5013 golang.org/x/crypto: GO-2026-5013 go.mod
HIGH GO-2026-5006 golang.org/x/crypto: GO-2026-5006 go.mod
HIGH GO-2026-5005 golang.org/x/crypto: GO-2026-5005 go.mod
HIGH DKC011 Database service publishes a host port docker-compose.yml:15
HIGH DKC011 Database service publishes a host port docker-compose.yml:5
MED SEC091 [SEC091] Go: net/http server without timeouts: HTTP server without ReadHeaderTimeout/Read… main.go:115
MED DKR003 Compose service `kafka` image uses the latest tag docker-compose.yml:15
MED DKR003 Compose service `zookeeper` image uses the latest tag docker-compose.yml:5
MED DKR007 Docker build context has no .dockerignore .dockerignore
MED DKC013 Database service has no persistent data volume docker-compose.yml:15
MED DKC013 Database service has no persistent data volume docker-compose.yml:5
LOW ERR003 [ERR003] Ignored Error (Go): Ignoring error return values. logging/logger.go:20
LOW DKC015 Database service has no healthcheck docker-compose.yml:15
LOW DKC015 Database service has no healthcheck docker-compose.yml:5
LOW DKC016 App service does not wait for database health docker-compose.yml:33
LOW DKC010 Compose service lacks no-new-privileges hardening docker-compose.yml:33
INFO MINED071 [MINED071] Go Panic Call: panic() crashes the process. Should return error in most cases. main.go:39
INFO MINED060 [MINED060] Go Context No Cancel: context.Background() at request handler boundary leaks g… prometheus/exporter.go:224
INFO MINED060 [MINED060] Go Context No Cancel: context.Background() at request handler boundary leaks g… main.go:55
Reset to top 5 44 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `redpanda-data/kminion`

**Score: 73/100 (C-)**  ·  44 findings  ·  scanned 2026-06-05 13:20 UTC  ·  6,760 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 30 |
| MEDIUM | 6 |
| LOW | 5 |

📊 [Full filterable report](https://repobility.com/scan/c58f3377-b01f-4e72-88bc-6df502faf969/)  ·  ![scorecard](https://repobility.com/scan/c58f3377-b01f-4e72-88bc-6df502faf969/report.png?v=1780665644-s2)

### Top findings

1. **HIGH** `MINED016` — Go Error Ignored
   `minion/offset_consumer.go:30` · CWE-754 · ✓ Repobility
2. **HIGH** `DKR014` — Dockerfile copies the entire context without .dockerignore
   `Dockerfile:18`
3. **HIGH** `MINED115` — Action `goreleaser/goreleaser-action` pinned to mutable ref `@v7`
   `.github/workflows/goreleaser.yml:18` · ✓ Repobility
4. **HIGH** `MINED115` — Action `actions/setup-go` pinned to mutable ref `@v6`
   `.github/workflows/goreleaser.yml:15` · ✓ Repobility
5. **HIGH** `MINED115` — Action `actions/checkout` pinned to mutable ref `@v6`
   `.github/workflows/goreleaser.yml:12` · ✓ Repobility

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/c58f3377-b01f-4e72-88bc-6df502faf969/_
Megaproject â high spam risk
Could not determine 'redpanda-data/kminion' 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.
Open in GitHub to file this issue 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.