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

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Config drift 1 finding

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

1 matching finding on this repo

medium Insecure pattern 'weak_hash' in docs/reference/configs/zarf/metallb/metallb-nat… docs/reference/configs/zarf/metallb/metallb-nativ…:638

View all config drift findings →

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.