← Back to scan
File as GitHub Issue repo: sebastienrousseau/dotfiles

Push this scan report to sebastienrousseau/dotfiles

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

Dockerfile copies broad context with incomplete .dockerignore

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 SECR001 Hardcoded secret in source config/gitleaks.toml:27
HIGH SUPC001 Supply chain — curl | bash anti-pattern scripts/tests/unit/test_install_edge_ca…:132
MED DKR001 Docker final stage has no non-root USER .devcontainer/Dockerfile:9
MED DKR014 Dockerfile copies broad context with incomplete .dockerignore tests/Dockerfile.sandbox:25
MED DKR014 Dockerfile copies broad context with incomplete .dockerignore Dockerfile.test:214
MED DKR014 Dockerfile copies broad context with incomplete .dockerignore Dockerfile.test:142
MED DKR014 Dockerfile copies broad context with incomplete .dockerignore Dockerfile.test:96
MED DKR014 Dockerfile copies broad context with incomplete .dockerignore Dockerfile.test:31
MED AGT015 Remote install command pipes network code directly to a shell .github/workflows/reusable-security-bas…:81
MED AGT015 Remote install command pipes network code directly to a shell .github/workflows/ci-enforced.yml:109
MED CRYP001 Crypto — plaintext HTTP for sensitive endpoint scripts/tests/unit/test_install_edge_ca…:96
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: `sebastienrousseau/dotfiles`

**Score: 80/100 (B+)**  ·  12 findings  ·  scanned 2026-05-14 21:41 UTC  ·  875 LOC

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

📊 [Full filterable report](https://repobility.com/scan/9a775c3b-246f-4433-aab8-71400ad1d310/)  ·  ![scorecard](https://repobility.com/scan/9a775c3b-246f-4433-aab8-71400ad1d310/report.png?v=1778794876-s2)

### Top findings

1. **CRITICAL** `SECR001` — Hardcoded secret in source
   `config/gitleaks.toml:27`
2. **HIGH** `SUPC001` — Supply chain — curl | bash anti-pattern
   `scripts/tests/unit/test_install_edge_cases.sh:132`
3. **MEDIUM** `DKR001` — Docker final stage has no non-root USER
   `.devcontainer/Dockerfile:9`
4. **MEDIUM** `DKR014` — Dockerfile copies broad context with incomplete .dockerignore
   `tests/Dockerfile.sandbox:25`
5. **MEDIUM** `DKR014` — Dockerfile copies broad context with incomplete .dockerignore
   `Dockerfile.test:214`

---

**Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately.

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/9a775c3b-246f-4433-aab8-71400ad1d310/_
Already filed
This repo publishes a SECURITY.md policy and the scan contains 1 Critical/High security finding(s). Public issue filing would violate coordinated disclosure. Submit privately via the project's security reporting channel.
Megaproject â high spam risk
Could not determine 'sebastienrousseau/dotfiles' 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
5/12 findings (42%) 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.