← Back to scan
File as GitHub Issue repo: base/node

Push this scan report to base/node

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 FROM `ubuntu:24.04` not pinned by digest

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 SEC009 [SEC009] .env File Committed: .env file with secrets committed to repository. .env
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… .env.mainnet:24
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… .env.sepolia:24
CRIT CORE_ENV_FILE .env file committed to repository .env
HIGH MINED118 Dockerfile FROM `ubuntu:24.04` not pinned by digest Dockerfile:41
HIGH MINED118 Dockerfile FROM `public.ecr.aws/docker/library/rust (no tag)` not pinned by digest Dockerfile:2
MED DKR001 Docker final stage has no non-root USER Dockerfile:42
LOW DKR008 .dockerignore misses sensitive defaults .dockerignore
LOW DKR011 Dockerfile installs recommended OS packages Dockerfile:44
LOW DKC010 Compose service lacks no-new-privileges hardening docker-compose.yml:17
LOW DKC010 Compose service lacks no-new-privileges hardening docker-compose.yml:1
LOW DKC006 Compose service does not declare a runtime user docker-compose.yml:17
LOW DKC006 Compose service does not declare a runtime user docker-compose.yml:1
Reset to top 5 13 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `base/node`

**Score: 56/100 (C+)**  ·  13 findings  ·  scanned 2026-06-05 08:42 UTC  ·  0 LOC

| Severity | Count |
|---|---|
| CRITICAL | 4 |
| HIGH | 2 |
| MEDIUM | 1 |
| LOW | 6 |

📊 [Full filterable report](https://repobility.com/scan/1297c01f-7581-4000-a049-19269cee9cf7/)  ·  ![scorecard](https://repobility.com/scan/1297c01f-7581-4000-a049-19269cee9cf7/report.png?v=1780648946-s2)

### Top findings

1. **CRITICAL** `SEC009` — .env File Committed: .env file with secrets committed to repository.
   `.env`
2. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive 
   `.env.mainnet:24`
3. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive 
   `.env.sepolia:24`
4. **CRITICAL** `CORE_ENV_FILE` — .env file committed to repository
   `.env`
5. **HIGH** `MINED118` — Dockerfile FROM `ubuntu:24.04` not pinned by digest
   `Dockerfile:41` · ✓ Repobility

---

**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/1297c01f-7581-4000-a049-19269cee9cf7/_
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 'base/node' 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 Filing guard overridden 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.