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.
Sign up free Scan another repo
55 of your 244 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 27.44s · analysis 17.79s · 28.9 MB · GitHub API rate-limit (preflight)

moby/moby

https://github.com/moby/moby · scanned 2026-06-05 08:19 UTC (5 days, 19 hours ago) · 10 languages

389 raw signals (185 security + 204 graph) 11/13 scanners ran 88th percentile · Go · large (100-500K LoC) System graph score 75 (higher by 15)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
83.2
/100
Security checks
92
48 findings
System graph
75
100.0% cov · 90 findings
Critical
3
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 80.0 0.20 16.00
documentation_score 85.0 0.15 12.75
practices_score 100.0 0.15 15.00
code_quality 80.0 0.10 8.00
Overall 1.00 89.5
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 12 Medium 59 Low 42 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 48 System graph 90 Crowd 0 Layer: Cicd 18 Quality 40 Security 32 Software 7 Api 1 Network 4 Hardware 35 Frontend 1
Scan summary Quality grade A- (90/100). Dimensions: security 100, maintainability 85. 185 findings (34 security). 378,339 lines analyzed.

Showing 107 of 138 actionable findings. 287 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

low Security checks cicd CI/CD security conf 0.35 ✓ Repobility 7 occurrences Workflow references repository secrets in a pull_request workflow
Fork pull_request runs do not receive normal repository secrets on GitHub Actions. Review this as a reliability/intent signal, not as direct fork-secret exfiltration. Raise severity only for pull_request_target or another trusted-context path that runs untrusted PR code with secrets.
4 files, 7 locations
.github/workflows/arm64.yml:139, 251 (2 hits)
.github/workflows/bin-image.yml:71, 72 (2 hits)
.github/workflows/test.yml:90, 99 (2 hits)
.github/workflows/windows-2025.yml:38
CI/CD securityworkflow secretsGitHub Actions
critical System graph security Secrets conf 1.00 Possible secret in daemon/volume/local/local.go
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
daemon/volume/local/local.go:460
critical System graph security Secrets conf 1.00 Possible secret in daemon/volume/local/local_unix.go
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
daemon/volume/local/local_unix.go:170
high Security checks software dependencies conf 0.90 ✓ Repobility 8 occurrences [MINED118] Dockerfile FROM `docker:17.12-dind` not pinned by digest: `FROM docker:17.12-dind` resolves the tag at build time. The registry CAN re-push a different image for the same tag, so every build is potentially different. Production images should pin to `image@sha256:...` for reproducibility + supply-chain integrity.
Replace with: `FROM docker:17.12-dind@sha256:<digest>`. Get the digest from `docker manifest inspect`. Re-pin via a scheduled bot (Renovate, Dependabot).
4 files, 8 locations
Dockerfile:78, 410, 412, 413, 635 (5 hits)
daemon/libnetwork/cmd/diagnostic/Dockerfile.dind:1
daemon/libnetwork/cmd/ssd/Dockerfile:1
daemon/libnetwork/support/Dockerfile:1
high Security checks software dependencies conf 0.90 ✓ Repobility 13 occurrences [MINED119] Dockerfile `ADD https://github.com/moby/busybox/releases/download/${BUSYBOX_VERSION}/busybox-w64-${BUSYBOX_VERSION}.exe`: Dockerfile `ADD <url>` downloads a remote artifact into the image with no integrity check. If the host or DNS is compromised between layers — or if the URL serves a different file later — malicious content gets baked into the image.
Download the file in CI with a known checksum, vendor it into the repo, and COPY it during the build. Or use `RUN curl -sSL URL | sha256sum -c <(echo '<expected> -')` to verify.
3 files, 13 locations
Dockerfile:112, 131, 146, 186, 196, 205, 252, 294, +3 more (11 hits)
contrib/busybox/Dockerfile:22
hack/dockerfiles/govulncheck.Dockerfile:11
high Security checks software Resource exhaustion conf 1.00 [SEC035] Unbounded Resource Allocation — DoS risk: Allocating resources (buffers, recursion stack, large ranges) based on user input without an upper bound. Attackers send `size=10000000` to exhaust memory, or trigger expensive computation. CWE-770/400. Examples: CVE-2023-44487 (HTTP/2 Rapid Reset), countless YAML/XML billion-laughs variants.
Cap user-controlled sizes BEFORE allocation: size = min(int(request.args.get('n', 100)), MAX_SIZE) Set framework-level limits: Flask: app.config['MAX_CONTENT_LENGTH'] = 10 * 1024 * 1024 FastAPI: use middleware to enforce request size Django: DATA_UPLOAD_MAX_MEMORY_SIZE in settings.py …
daemon/attach.go:27
high Security checks cicd CI/CD security conf 1.00 3 occurrences [SEC069] Dockerfile: no USER directive (runs as root): Container runs as root because no USER directive was set. Ported from trivy DS002 / checkov CKV_DOCKER_3 (Apache-2.0). Implement as a file-level rule: skip if file contains `^\s*USER\s+\S+` other than `root`.
Add `RUN adduser -D app && USER app` before the CMD/ENTRYPOINT.
3 files, 3 locations
daemon/builder/dockerfile/buildargs.go:1
daemon/builder/dockerfile/builder_windows.go:1
daemon/builder/dockerfile/containerbackend.go:1
CI/CD securitycontainers
high Security checks quality Quality conf 1.00 [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} disables certificate verification — MITM risk. Ported from gosec G402 (Apache-2.0).
Remove the option. If self-signed certs are required, pin via RootCAs.
pkg/plugins/plugins.go:117
low Security checks quality Quality conf 1.00 3 occurrences [SEC093] Go: exec.Command with non-literal: exec.Command(<var>) — variable command name allows command injection. Ported from gosec G204 (Apache-2.0).
Use a constant command name and validate args via a whitelist.
3 files, 3 locations
daemon/internal/quota/testhelpers.go:61
daemon/internal/usergroup/add_linux.go:88
daemon/internal/usergroup/lookup_unix.go:105
high System graph security security conf 1.00 Insecure pattern 'exec_used' in daemon/libnetwork/iptables/iptables.go:489
Found a known-risky pattern (exec_used). Review and replace if possible.
daemon/libnetwork/iptables/iptables.go:489 Exec used
medium Security checks cicd CI/CD security conf 0.94 2 occurrences Compose service `jaeger` image uses the latest tag
Pin to a maintained version tag or digest and update it deliberately through dependency automation.
lines 4, 18
contrib/otel/compose.yaml:4, 18 (2 hits)
CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.82 19 occurrences Docker final stage has no non-root USER
Add a non-root USER in the final runtime stage after files and permissions are prepared.
12 files, 12 locations
Dockerfile:644
Dockerfile.simple:13
Dockerfile.windows:159
api/Dockerfile:23
contrib/busybox/Dockerfile:18
contrib/nnp-test/Dockerfile:5
contrib/syscall-test/Dockerfile:5
daemon/libnetwork/cmd/diagnostic/Dockerfile.client:1
CI/CD securitycontainers
medium Security checks cicd CI/CD security conf 0.84 16 occurrences Dockerfile ADD downloads remote content
Use curl/wget with a pinned URL, verify checksum or signature, and prefer COPY for local files.
4 files, 16 locations
Dockerfile:68, 112, 131, 146, 186, 196, 205, 252, +4 more (12 hits)
vendor/github.com/moby/policy-helpers/Dockerfile:11, 26 (2 hits)
Dockerfile.simple:40
contrib/busybox/Dockerfile:22
CI/CD securitycontainers
medium Security checks cicd CI/CD security conf 0.76 8 occurrences Dockerfile copies broad context with incomplete .dockerignore
Tighten .dockerignore or replace COPY . with explicit COPY statements.
7 files, 8 locations
Dockerfile:629, 645 (2 hits)
Dockerfile.simple:61
Dockerfile.windows:312
contrib/nnp-test/Dockerfile:8
contrib/syscall-test/Dockerfile:8
man/vendor/github.com/cpuguy83/go-md2man/v2/Dockerfile:4
vendor/github.com/pelletier/go-toml/Dockerfile:3
CI/CD securitycontainers
medium Security checks cicd CI/CD security conf 0.86 Dockerfile separates apt update from install
Combine update and install in the same RUN instruction and clean package indexes in that layer.
cmd/dockerd/winresources/Dockerfile:15 CI/CD securitycontainers
medium Security checks cicd CI/CD security conf 0.88 Heavy generated directories are included in Docker build context
Add these paths to .dockerignore or move runtime data outside the repository root used as the Docker build context.
.dockerignore CI/CD securitycontainers
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: busybox
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:50 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: containerd-${TARGETOS}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:182 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: containerutil-${TARGETOS}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:411 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: containerutil-windows-${TARGETARCH}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:410 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: delve-${DELVE_SUPPORTED}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:126 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: dev-firewalld-${FIREWALLD}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:466 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: dev-systemd-${SYSTEMD}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:458 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: rootlesskit-${TARGETOS}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:360 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: runc-${TARGETOS}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:286 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: tini-${TARGETOS}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:320 containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 13 occurrences Dockerfile ADD downloads remote content without checksum
Remote build inputs can change or be replaced upstream. Use Dockerfile ADD --checksum or download with an explicit digest/signature verification step.
2 files, 13 locations
Dockerfile:68, 112, 131, 146, 186, 196, 205, 252, +4 more (12 hits)
contrib/busybox/Dockerfile:22
containersChecksum
medium System graph hardware Security conf 1.00 Dockerfile runs as root: api/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: cmd/dockerd/winresources/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: contrib/busybox/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: contrib/nnp-test/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: contrib/syscall-test/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: daemon/libnetwork/cmd/networkdb-test/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: daemon/libnetwork/cmd/ssd/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: daemon/libnetwork/support/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/bin-image.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.32.yaml:4096
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.32.yaml:4096 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.33.yaml:4100
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.33.yaml:4100 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.34.yaml:4128
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.34.yaml:4128 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.35.yaml:4132
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.35.yaml:4132 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.36.yaml:4153
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.36.yaml:4153 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.37.yaml:4173
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.37.yaml:4173 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.38.yaml:4219
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.38.yaml:4219 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.39.yaml:5502
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.39.yaml:5502 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.40.yaml:5646
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.40.yaml:5646 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.41.yaml:5900
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.41.yaml:5900 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.42.yaml:5893
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.42.yaml:5893 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.43.yaml:5926
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.43.yaml:5926 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.44.yaml:6065
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.44.yaml:6065 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.45.yaml:6051
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.45.yaml:6051 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.46.yaml:6162
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.46.yaml:6162 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.47.yaml:6184
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.47.yaml:6184 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.48.yaml:7220
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.48.yaml:7220 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.49.yaml:7227
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.49.yaml:7227 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.50.yaml:7057
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.50.yaml:7057 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.51.yaml:7078
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.51.yaml:7078 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.52.yaml:7368
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.52.yaml:7368 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.53.yaml:7616
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.53.yaml:7616 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/docs/v1.54.yaml:7616
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/docs/v1.54.yaml:7616 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in api/swagger.yaml:7616
Found a known-risky pattern (weak_hash). Review and replace if possible.
api/swagger.yaml:7616 Weak hash
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — daemon/libnetwork/cmd/ssd/ssd.py:37
`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph network Security conf 1.00 Privileged port 256 in use
Port 256 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
Dockerfile Ports
medium System graph network Security conf 1.00 Privileged port 50 in use
Port 50 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
Dockerfile Ports
medium System graph network Security conf 1.00 Privileged port 95 in use
Port 95 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
Dockerfile Ports
low Security checks cicd CI/CD security conf 0.72 .dockerignore misses sensitive defaults
Add missing patterns such as .env, .git, private keys, certificates, dependency folders, and local databases.
.dockerignore CI/CD securitycontainers
low Security checks quality Error handling conf 1.00 3 occurrences [ERR003] Ignored Error (Go): Ignoring error return values.
Handle the error or use errcheck linter.
3 files, 3 locations
client/container_wait.go:80
client/hijack.go:56
client/internal/jsonmessages.go:54
low Security checks cicd CI/CD security conf 1.00 3 occurrences [SEC075] Dockerfile: no HEALTHCHECK: No HEALTHCHECK directive — orchestrators can't detect a wedged process. Ported from trivy DS026 / checkov CKV_DOCKER_2 (Apache-2.0). Implement file-level: skip if file contains `^\s*HEALTHCHECK\b`.
Add `HEALTHCHECK CMD curl -f http://localhost:PORT/health || exit 1`.
3 files, 3 locations
daemon/builder/dockerfile/buildargs.go:1
daemon/builder/dockerfile/builder_windows.go:1
daemon/builder/dockerfile/containerbackend.go:1
CI/CD securitycontainers
low Security checks cicd CI/CD security conf 1.00 [SEC077] Dockerfile: MAINTAINER directive (deprecated): MAINTAINER is deprecated in favour of LABEL maintainer=. Ported from checkov CKV_DOCKER_6 (Apache-2.0).
Replace `MAINTAINER name <email>` with `LABEL maintainer="name <email>"`.
daemon/builder/dockerfile/evaluator.go:110 CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.56 3 occurrences Compose service does not declare a runtime user
Set a non-root `user:` in Compose or ensure the final image stage has a non-root USER directive.
lines 4, 10, 18
contrib/otel/compose.yaml:4, 10, 18 (3 hits)
CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.62 3 occurrences Compose service lacks no-new-privileges hardening
Add `security_opt: ["no-new-privileges:true"]` unless the service has a documented need for privilege escalation.
lines 4, 10, 18
contrib/otel/compose.yaml:4, 10, 18 (3 hits)
CI/CD securitycontainers
high Security checks cicd CI/CD security conf 0.72 2 occurrences Dockerfile keeps pip download cache
Use `pip install --no-cache-dir ...` in container builds.
lines 22, 33
daemon/libnetwork/cmd/ssd/Dockerfile:22, 33 (2 hits)
CI/CD securitycontainers
low Security checks cicd CI/CD security conf 0.74 15 occurrences Dockerfile leaves apt package indexes in the image layer
End the apt install layer with `rm -rf /var/lib/apt/lists/*`.
3 files, 15 locations
Dockerfile:64, 69, 85, 151, 257, 298, 331, 365, +5 more (13 hits)
contrib/nnp-test/Dockerfile:6
contrib/syscall-test/Dockerfile:6
CI/CD securitycontainers
low Security checks quality Quality conf 0.60 8 occurrences Duplicated implementation block across source files
Duplicate implementation blocks are maintenance debt. Keep them visible, but they are not a high-severity defect unless the duplicated logic is security-sensitive or drifting.
8 files, 8 locations
api/types/container/hostconfig_windows.go:21
client/internal/jsonmessages.go:75
client/pkg/streamformatter/streamformatter.go:103
client/service_create.go:30
client/service_logs.go:25
contrib/syscall-test/userns.c:1
daemon/container_operations_windows.go:44
daemon/graphdriver/overlay2/overlay.go:101
duplicationquality
low Security checks quality Quality conf 0.68 Multiple AI-agent scaffold marker files are present
Keep one current agent instruction file if it helps contributors, remove stale progress/completion markers, and make sure the README, tests, and CI describe the real supported behavior.
.github/copilot-instructions.md:1
high Security checks quality Quality conf 0.62 8 occurrences Source file name looks like an AI patch artifact
Rename it to the domain concept it implements or merge it into the existing module it was meant to change.
8 files, 8 locations
client/config_update.go:1
client/container_copy.go:1
client/node_update.go:1
client/secret_update.go:1
client/service_update.go:1
client/swarm_update.go:1
client/volume_update.go:1
daemon/volume/mounts/volume_copy.go:1
low System graph quality Maintenance conf 1.00 444 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: alpine:3.23
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
daemon/libnetwork/cmd/ssd/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: debian:${BASE_DEBIAN_DISTRO}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:84 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: debian:${DEBIAN_VERSION}-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
cmd/dockerd/winresources/Dockerfile:11 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: distribution/distribution:${REGISTRY_VERSION}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:78 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: docker/buildx-bin:${BUILDX_VERSION}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:412 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: docker/compose-bin:${COMPOSE_VERSION}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:413 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: docker:18-dind
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
daemon/libnetwork/support/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: docker:dind
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:635 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: golang:${GO_VERSION}-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
api/Dockerfile:4 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: tonistiigi/xx:${XX_VERSION}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:46 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: tonistiigi/xx:${XX_VERSION}
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
cmd/dockerd/winresources/Dockerfile:10 containersPinned dependencies
low System graph software Dead code candidate conf 1.00 File has no detected symbols: daemon/libnetwork/cmd/ssd/ssd.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph quality Complexity conf 1.00 Very large file: daemon/daemon.go (1931 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: daemon/daemon_unix.go (1644 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: daemon/libnetwork/drivers/bridge/bridge_linux.go (1921 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: daemon/libnetwork/libnetwork_linux_test.go (1621 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: daemon/libnetwork/network.go (2204 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: daemon/libnetwork/networkdb/networkdb.pb.go (3091 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: daemon/logger/awslogs/cloudwatchlogs_test.go (1725 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration-cli/docker_api_containers_test.go (1779 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration-cli/docker_cli_build_test.go (6251 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration-cli/docker_cli_daemon_test.go (2255 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration-cli/docker_cli_network_unix_test.go (1814 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration-cli/docker_cli_run_test.go (4377 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration-cli/docker_cli_run_unix_test.go (1596 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration-cli/docker_cli_swarm_test.go (2050 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration/networking/bridge_linux_test.go (2282 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integration/networking/port_mapping_linux_test.go (1603 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: internal/namesgenerator/names-generator.go (860 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/fb0932ce-efa0-403b-a495-6413b4e72fc7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/fb0932ce-efa0-403b-a495-6413b4e72fc7/

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.