DoD-Platform-One/bigbang

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

Scan timing: clone 3.1s · analysis 1.05s · 4.5 MB · GitHub API rate-limit (preflight)

https://github.com/DoD-Platform-One/bigbang · scanned 2026-06-05 18:33 UTC (4 days, 18 hours ago) · 10 languages

36 raw signals (12 security + 24 graph) 10th percentile · Unknown · System graph score 85 (lower by 24)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 18 hours ago · v2 · 18 actionable findings from 2 signal sources. 6 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 12 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	30.0	0.15	4.50
`security_score`	45.0	0.25	11.25
`testing_score`	70.0	0.20	14.00
`documentation_score`	85.0	0.15	12.75
`practices_score`	70.0	0.15	10.50
`code_quality`	77.8	0.10	7.78
Overall		1.00	60.8

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 8 High 3 Medium 4 Low 1 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 6 System graph 12 Crowd 0 Layer: Quality 2 Security 12 Api 1 Network 1 Frontend 1 Cicd 1

Exclude dismissed / FP Exclude test files

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

Possible secret in docs/reference/scripts/airgap-dev/package-repos.sh

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in docs/reference/scripts/airgap-dev/package-repos.sh:10; move to env var / secrets manager.

docs/reference/scripts/airgap-dev/package-repos.sh:10

Possible secret in docs/reference/scripts/developer/k3d-dev.sh

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in docs/reference/scripts/developer/k3d-dev.sh:843; move to env var / secrets manager.

docs/reference/scripts/developer/k3d-dev.sh:843

Possible secret in scripts/install_flux.sh

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in scripts/install_flux.sh:50; move to env var / secrets manager.

scripts/install_flux.sh:50

Possible secret in chart/values.yaml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in chart/values.yaml:2360; move to env var / secrets manager.

chart/values.yaml:2360

Insecure pattern 'private_key_in_repo' in chart/ingress-certs.yaml:9

GapSeverity.CRITICAL Layer.SECURITY score 0.550

Why: critical severity · OWASP-class risk

chart/ingress-certs.yaml:9

Privileged port 1000 in use

GapSeverity.MEDIUM Layer.NETWORK score 0.338

Why: medium severity · misconfigured network surface

Fix: If the number in docs/reference/scripts/developer/k3d-dev.sh is a real port, change the binding to ≥1024 or run behind a proxy.

docs/reference/scripts/developer/k3d-dev.sh

Insecure pattern 'weak_hash' in base/flux/gotk-components.yaml:4828

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

base/flux/gotk-components.yaml:4828

Insecure pattern 'weak_hash' in docs/reference/configs/zarf/metallb/metallb-native-0.13.9.yaml:638

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

docs/reference/configs/zarf/metallb/metallb-native-0.13.9.yaml:638

No CI/CD pipelines detected

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

#10

Very large file: docs/reference/scripts/developer/k3d-dev.sh (1596 lines)

GapSeverity.LOW Layer.QUALITY score 0.100

Why: low severity

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/9cd71d44-cae5-42c5-8ec6-b380cbe0bd7b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9cd71d44-cae5-42c5-8ec6-b380cbe0bd7b/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.