← Back to scan
File as GitHub Issue repo: ethteck/coddog

Push this scan report to ethteck/coddog

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

Docker build context has no .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
HIGH DKR014 Dockerfile copies the entire context without .dockerignore deployment/Dockerfile.db-cli:15
HIGH DKR014 Dockerfile copies the entire context without .dockerignore deployment/Dockerfile.api:13
HIGH DKC011 Database service publishes a host port deployment/docker-compose.yml:2
MED DKR017 Dockerfile installs dependencies after copying the full source tree deployment/Dockerfile.db-cli:16
MED DKR007 Docker build context has no .dockerignore .dockerignore
MED DKR017 Dockerfile installs dependencies after copying the full source tree deployment/Dockerfile.api:14
MED DKR001 Docker final stage has no non-root USER deployment/Dockerfile.frontend:32
LOW AIC003 Duplicated implementation block across source files website/src/components/SymbolLabelOther…:24
LOW DKC015 Database service has no healthcheck deployment/docker-compose.yml:84
LOW DKR011 Dockerfile installs recommended OS packages deployment/Dockerfile.db-cli:20
LOW DKR011 Dockerfile installs recommended OS packages deployment/Dockerfile.db-cli:7
LOW DKR011 Dockerfile installs recommended OS packages deployment/Dockerfile.api:18
LOW DKR011 Dockerfile installs recommended OS packages deployment/Dockerfile.api:7
LOW DKC010 Compose service lacks no-new-privileges hardening deployment/docker-compose.yml:60
LOW DKC010 Compose service lacks no-new-privileges hardening deployment/docker-compose.yml:31
LOW DKC017 Database password is wired through an environment variable placeholder deployment/docker-compose.yml:2
LOW DKC006 Compose service does not declare a runtime user deployment/docker-compose.yml:60
Reset to top 5 17 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `ethteck/coddog`

**Score: 80/100 (C+)**  ·  17 findings  ·  scanned 2026-05-17 20:26 UTC  ·  6,883 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 3 |
| MEDIUM | 4 |
| LOW | 10 |

📊 [Full filterable report](https://repobility.com/scan/18ce706c-28da-4c62-863a-0dbc3946238b/)  ·  ![scorecard](https://repobility.com/scan/18ce706c-28da-4c62-863a-0dbc3946238b/report.png?v=1779049567-s2)

### Top findings

1. **HIGH** `DKR014` — Dockerfile copies the entire context without .dockerignore
   `deployment/Dockerfile.db-cli:15`
2. **HIGH** `DKR014` — Dockerfile copies the entire context without .dockerignore
   `deployment/Dockerfile.api:13`
3. **HIGH** `DKC011` — Database service publishes a host port
   `deployment/docker-compose.yml:2`
4. **MEDIUM** `DKR017` — Dockerfile installs dependencies after copying the full source tree
   `deployment/Dockerfile.db-cli:16`
5. **MEDIUM** `DKR007` — Docker build context has no .dockerignore
   `.dockerignore`

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/18ce706c-28da-4c62-863a-0dbc3946238b/_
Megaproject â high spam risk
Could not determine 'ethteck/coddog' 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.