← Back to scan
File as GitHub Issue repo: lensesio/fast-data-dev

Push this scan report to lensesio/fast-data-dev

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

Database service publishes a host port

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 DKC013 Database service has no persistent data volume examples/fdd-mongo/docker-compose.yml:21
HIGH DKC013 Database service has no persistent data volume examples/fdd-mongo/docker-compose.yml:14
HIGH DKR004 Docker build secret exposed through ARG Dockerfile:89
HIGH DKR004 Docker build secret exposed through ARG Dockerfile:88
HIGH DKC011 Database service publishes a host port examples/fdd-mongo/docker-compose.yml:14
HIGH DKC011 Database service publishes a host port examples/fdd-mongo/docker-compose.yml:2
HIGH DKC011 Database service publishes a host port examples/fdd-acls/docker-compose.yml:2
MED DKR003 Compose service `lenses-dev` image uses the latest tag examples/fdd-mongo/docker-compose.yml:2
MED DKR002 Compose service `mongo` image has no explicit tag examples/fdd-mongo/docker-compose.yml:21
MED DKR002 Compose service `mongo-express` image has no explicit tag examples/fdd-mongo/docker-compose.yml:14
MED DKR002 Compose service `lenses-dev` image has no explicit tag examples/fdd-acls/docker-compose.yml:2
MED DKR007 Docker build context has no .dockerignore .dockerignore
MED DKC015 Database service has no healthcheck examples/fdd-mongo/docker-compose.yml:21
MED DKC015 Database service has no healthcheck examples/fdd-mongo/docker-compose.yml:14
MED DKR001 Docker final stage has no non-root USER Dockerfile:220
MED DKC013 Database service has no persistent data volume examples/fdd-mongo/docker-compose.yml:2
MED DKC013 Database service has no persistent data volume examples/fdd-acls/docker-compose.yml:2
MED DKC007 Compose service contains a literal secret environment value examples/fdd-acls/docker-compose.yml:2
MED CORE_NO_CI No CI/CD configuration found —
LOW DKC015 Database service has no healthcheck examples/fdd-mongo/docker-compose.yml:2
LOW DKC015 Database service has no healthcheck examples/fdd-acls/docker-compose.yml:2
LOW DKR011 Dockerfile installs recommended OS packages Dockerfile:232
LOW DKR011 Dockerfile installs recommended OS packages Dockerfile:7
Reset to top 5 23 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `lensesio/fast-data-dev`

**Score: 75/100 (C-)**  ·  24 findings  ·  scanned 2026-05-16 00:58 UTC  ·  75 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 7 |
| MEDIUM | 12 |
| LOW | 4 |

📊 [Full filterable report](https://repobility.com/scan/3af2bca0-4d6c-49c6-90f4-971e0cc6fd30/)  ·  ![scorecard](https://repobility.com/scan/3af2bca0-4d6c-49c6-90f4-971e0cc6fd30/report.png?v=1778893096-s2)

### Top findings

1. **HIGH** `DKC013` — Database service has no persistent data volume
   `examples/fdd-mongo/docker-compose.yml:21`
2. **HIGH** `DKC013` — Database service has no persistent data volume
   `examples/fdd-mongo/docker-compose.yml:14`
3. **HIGH** `DKR004` — Docker build secret exposed through ARG
   `Dockerfile:89`
4. **HIGH** `DKR004` — Docker build secret exposed through ARG
   `Dockerfile:88`
5. **HIGH** `DKC011` — Database service publishes a host port
   `examples/fdd-mongo/docker-compose.yml:14`

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/3af2bca0-4d6c-49c6-90f4-971e0cc6fd30/_
Already filed
Repobility already filed issue #202 on this repo on 2026-05-17. Filing again would be duplicate spam.
View existing issue
Megaproject â high spam risk
Could not determine 'lensesio/fast-data-dev' 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
16/24 findings (67%) 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.