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
19 of your 59 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

podman-container-tools/podman

https://github.com/podman-container-tools/podman · scanned 2026-06-05 13:17 UTC (5 days, 6 hours ago) · 10 languages

196 raw signals (56 security + 140 graph) 11/13 scanners ran 56th percentile · Go · medium (20-100K LoC)

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

Complete repo analysis

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

JSON
Combined
77.5
/100
Security checks
85
21 findings
System graph
70
88.9% cov · 60 findings
Critical
2
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 27.0 0.20 5.40
documentation_score 68.0 0.15 10.20
practices_score 60.0 0.15 9.00
code_quality 80.0 0.10 8.00
Overall 1.00 70.3
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 2 High 5 Medium 21 Low 36 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 21 System graph 60 Crowd 0 Layer: Quality 50 Software 6 Security 6 Cicd 2 Network 4 Hardware 12 Frontend 1
Scan summary Quality grade B (70/100). Dimensions: security 100, maintainability 85. 56 findings (3 security). 35,419 lines analyzed.

Showing 57 of 81 actionable findings. 122 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 2 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.
lines 169, 311
.github/workflows/cherry-pick.yml:169, 311 (2 hits)
CI/CD securityworkflow secretsGitHub Actions
critical System graph security Secrets conf 1.00 Possible secret in pkg/lookup/lookup.go
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
pkg/lookup/lookup.go:14
critical System graph security Secrets conf 1.00 Possible secret in pkg/util/utils.go
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
pkg/util/utils.go:136
high Security checks quality Quality conf 1.00 ✓ Repobility [MINED108] `self.state` used but never assigned in __init__: Method `run` of class `APIVersionsDirective` reads `self.state`, but no assignment to it exists in __init__ (and no class-level fallback). This raises AttributeError the first time the method runs against an instance.
Initialize `self.state = <default>` in __init__, or add a class-level default.
docs/source/conf.py:122
high System graph security security conf 1.00 Insecure pattern 'exec_used' in cmd/podman/containers/exec.go:128
Found a known-risky pattern (exec_used). Review and replace if possible.
cmd/podman/containers/exec.go:128 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in libpod/sqlite_state_internal.go:570
Found a known-risky pattern (exec_used). Review and replace if possible.
libpod/sqlite_state_internal.go:570 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in pkg/api/tags.yaml:24
Found a known-risky pattern (exec_used). Review and replace if possible.
pkg/api/tags.yaml:24 Exec used
medium Security checks quality Practices conf 1.00 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build artifacts.
Add a .gitignore appropriate for your language/framework.
medium Security checks quality Quality conf 0.78 Suspicious implementation file appears unreferenced
Confirm whether this file is reachable. If not, delete it; if yes, wire it through explicit imports, routes, or entry points and add a test that proves the path executes.
cmd/podman/auto-update.go:1
medium System graph hardware Supply chain conf 1.00 4 occurrences Docker base image uses a mutable or implicit tag: quay.io/libpod/podman_python
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
4 files, 4 locations
test/compose/env_and_volume/read/Dockerfile:1
test/compose/env_and_volume/write/Dockerfile:1
test/compose/mount_and_label/frontend/Dockerfile:1
test/compose/port_map_diff_port/frontend/Dockerfile:1
containersPinned dependencies
medium System graph hardware Security conf 1.00 Dockerfile runs as root: test/compose/env_and_volume/read/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: test/compose/env_and_volume/write/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: test/compose/mount_and_label/frontend/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: test/compose/port_map_diff_port/frontend/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: test/compose/simple_port_map/frontend/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: test/compose/uptwice/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: test/python/docker/build_labels/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 4 occurrences 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.
4 files, 4 locations
.github/workflows/cherry-pick.yml
.github/workflows/dev-bump.yml
.github/workflows/release.yml
.github/workflows/update-podmanio.yml
CI/CD securitySupply chainGithub actions
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — docs/source/conf.py:38
`subprocess.Popen(...)` 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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — test/apiv2/python/rest_api/v1_test_rest_v1_0_0.py:48
`requests.get(...)` 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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — test/python/docker/__init__.py:77
`subprocess.Popen(...)` 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
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
cmd/podman-mac-helper/main.go:133
cmd/podman/artifact/add.go:45
cmd/podman/artifact/extract.go:33
low Security checks quality Quality conf 0.60 23 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.
12 files, 17 locations
cmd/podman/containers/stop.go:1, 5, 101 (3 hits)
cmd/podman/containers/restart.go:1, 102 (2 hits)
cmd/podman/containers/unpause.go:1, 93 (2 hits)
cmd/podman/images/push.go:2, 4 (2 hits)
cmd/podman/artifact/push.go:1
cmd/podman/containers/pause.go:95
cmd/podman/containers/unmount.go:1
cmd/podman/images/mount.go:97
duplicationquality
high Security checks quality Quality conf 0.62 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.
cmd/podman/auto-update.go:1
low System graph quality Maintenance conf 1.00 307 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 software Dead code candidate conf 1.00 File has no detected symbols: test/python/docker/compat/constant.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: test/compose/simple_port_map/frontend/app.py:hello, test/compose/port_map_diff_port/frontend/app.py:hello This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why t…
5 occurrences
repo-level (5 hits)
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: convert_markdown_title
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
docs/source/conf.py:97
low System graph software Dead code conf 1.00 Possibly dead Python function: setup
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
docs/source/conf.py:139
low System graph quality Complexity conf 1.00 Very large file: cmd/podman/common/completion.go (2042 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: libpod/container_internal.go (3014 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: libpod/container_internal_common.go (3191 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: libpod/namesgenerator/names-generator.go (865 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: libpod/oci_conmon_common.go (1656 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: libpod/options.go (2285 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: libpod/sqlite_state.go (2333 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: libpod/state_test.go (2446 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: pkg/api/server/register_containers.go (1914 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: pkg/api/server/register_images.go (2322 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: pkg/domain/infra/abi/containers.go (1886 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: pkg/domain/infra/abi/play.go (1934 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: pkg/k8s.io/api/core/v1/types.go (5847 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: pkg/k8s.io/apimachinery/pkg/apis/meta/v1/types.go (1346 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: pkg/systemd/generate/containers_test.go (1805 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: pkg/systemd/quadlet/quadlet.go (2444 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/e2e/build_test.go (1447 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/e2e/checkpoint_test.go (1838 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/e2e/common_test.go (1885 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/e2e/generate_kube_test.go (2004 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/e2e/play_kube_test.go (6529 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/e2e/pod_create_test.go (1439 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/e2e/quadlet_test.go (1374 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/e2e/run_networking_test.go (1684 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/e2e/run_test.go (2463 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/e2e/run_volume_test.go (1257 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/system/helpers.bash (1512 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/921f2ee3-abc8-491a-9606-0dbbad94170d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/921f2ee3-abc8-491a-9606-0dbbad94170d/

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.