← Back to scan
File as GitHub Issue repo: devops-infra/action-pull-request

Push this scan report to devops-infra/action-pull-request

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 `devops-infra/triglav/.github/workflows/e2e-action-pull-request.yml` pinned to muta

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 MINED021 [MINED021] Path Traversal Os Join: os.path.join(user_dir, filename) where filename can co… scripts/split_content_bytes.py:60
HIGH MINED115 Action `devops-infra/.github/.github/workflows/reusable-auto-release-create.yml` pinned t… .github/workflows/auto-release-create.y…:29
HIGH MINED115 Action `devops-infra/.github/.github/workflows/reusable-cron-dependency-update.yml` pinne… .github/workflows/cron-dependency-updat…:16
HIGH MINED115 Action `devops-infra/.github/.github/workflows/reusable-manual-release-create.yml` pinned… .github/workflows/manual-release-create…:33
HIGH MINED115 Action `devops-infra/triglav/.github/workflows/e2e-action-pull-request.yml` pinned to mut… .github/workflows/manual-e2e-validate.y…:28
HIGH MINED115 Action `devops-infra/.github/.github/workflows/reusable-auto-pull-request-create.yml` pin… .github/workflows/auto-pull-request-cre…:19
HIGH MINED115 Action `devops-infra/.github/.github/workflows/reusable-manual-release-branch-prepare.yml… .github/workflows/manual-release-branch…:34
HIGH MINED131 pre-commit hook `https://github.com/pre-commit/pre-commit-hooks` pinned to mutable rev `v… .pre-commit-config.yaml:2
HIGH MINED118 Dockerfile FROM `alpine:3.23.4` not pinned by digest Dockerfile:1
MED DKR001 Docker final stage has no non-root USER Dockerfile:1
LOW COMP001 [COMP001] High cognitive complexity: Function `split_chunks` has cognitive complexity 8 (… scripts/split_content_bytes.py:26
LOW DKR008 .dockerignore misses sensitive defaults .dockerignore
Reset to top 5 12 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `devops-infra/action-pull-request`

**Score: 77/100 (A-)**  ·  12 findings  ·  scanned 2026-06-05 17:38 UTC  ·  157 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 9 |
| MEDIUM | 1 |
| LOW | 2 |

📊 [Full filterable report](https://repobility.com/scan/2368cd81-0e9f-4d73-a031-6ca41589207d/)  ·  ![scorecard](https://repobility.com/scan/2368cd81-0e9f-4d73-a031-6ca41589207d/report.png?v=1780681131-s2)

### Top findings

1. **HIGH** `MINED021` — Path Traversal Os Join
   `scripts/split_content_bytes.py:60` · CWE-22 · ✓ Repobility
2. **HIGH** `MINED115` — Action `devops-infra/.github/.github/workflows/reusable-auto-release-create.yml` pinned to
   `.github/workflows/auto-release-create.yml:29` · ✓ Repobility
3. **HIGH** `MINED115` — Action `devops-infra/.github/.github/workflows/reusable-cron-dependency-update.yml` pinned
   `.github/workflows/cron-dependency-update.yml:16` · ✓ Repobility
4. **HIGH** `MINED115` — Action `devops-infra/.github/.github/workflows/reusable-manual-release-create.yml` pinned 
   `.github/workflows/manual-release-create.yml:33` · ✓ Repobility
5. **HIGH** `MINED115` — Action `devops-infra/triglav/.github/workflows/e2e-action-pull-request.yml` pinned to muta
   `.github/workflows/manual-e2e-validate.yml:28` · ✓ Repobility

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/2368cd81-0e9f-4d73-a031-6ca41589207d/_
Megaproject â high spam risk
Could not determine 'devops-infra/action-pull-request' 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
6/12 findings (50%) 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.
I read the warnings â override 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.