← Back to scan
File as GitHub Issue repo: DoD-Platform-One/bigbang

Push this scan report to DoD-Platform-One/bigbang

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

Identified a Private Key, which may compromise cryptographic security and sensitive data e

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 private-key Identified a Private Key, which may compromise cryptographic security and sensitive data … docs/installation/environments/airgap.md:426
CRIT private-key Identified a Private Key, which may compromise cryptographic security and sensitive data … docs/configuration/sample-prod-config.md:162
CRIT curl-auth-user Discovered a potential basic authorization token provided in a curl command, which could … docs/packages/core/twistlock.md:101
CRIT private-key Identified a Private Key, which may compromise cryptographic security and sensitive data … docs/configuration/gateways.md:171
CRIT private-key Identified a Private Key, which may compromise cryptographic security and sensitive data … docs/reference/configs/example/vault-pr…:9
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… docs/community/development/package-inte…:136
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… docs/community/development/package-inte…:48
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… chart/templates/backstage/values.yaml:114
CRIT private-key Identified a Private Key, which may compromise cryptographic security and sensitive data … chart/ingress-certs.yaml:9
HIGH SEC113 [SEC113] SSH host-key verification disabled (MITM): Accepting any SSH host key on first c… docs/reference/scripts/airgap-zarf/zarf…:27
HIGH SEC021 [SEC021] Shell Trace Around Secret Handling: Shell xtrace is enabled near secret handling… docs/reference/scripts/airgap-dev/packa…:3
MED AGT012 Agent control bridge may listen on a network interface without visible auth chart/templates/gatekeeper/values.yaml:65
Reset to top 5 12 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `DoD-Platform-One/bigbang`

**Score: 65/100 (C+)**  ·  12 findings  ·  scanned 2026-06-05 18:33 UTC  ·  0 LOC

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

📊 [Full filterable report](https://repobility.com/scan/9cd71d44-cae5-42c5-8ec6-b380cbe0bd7b/)  ·  ![scorecard](https://repobility.com/scan/9cd71d44-cae5-42c5-8ec6-b380cbe0bd7b/report.png?v=1780684397-s2)

### Top findings

1. **CRITICAL** `private-key` — Identified a Private Key, which may compromise cryptographic security and sensitive data e
   `docs/installation/environments/airgap.md:426`
2. **CRITICAL** `private-key` — Identified a Private Key, which may compromise cryptographic security and sensitive data e
   `docs/configuration/sample-prod-config.md:162`
3. **CRITICAL** `curl-auth-user` — Discovered a potential basic authorization token provided in a curl command, which could c
   `docs/packages/core/twistlock.md:101`
4. **CRITICAL** `private-key` — Identified a Private Key, which may compromise cryptographic security and sensitive data e
   `docs/configuration/gateways.md:171`
5. **CRITICAL** `private-key` — Identified a Private Key, which may compromise cryptographic security and sensitive data e
   `docs/reference/configs/example/vault-production-values.yaml:9`

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/9cd71d44-cae5-42c5-8ec6-b380cbe0bd7b/_
Megaproject â high spam risk
Could not determine 'DoD-Platform-One/bigbang' 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
10/16 findings (62%) 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.