Security Deep Dive
Podman
Security posture and CVE patch evidence from tracked releases.
No CVEs tracked against v5.8.2.
Trust Signals — 4 of 9 Present
Evidence already collected from releases and repository metadata.
Security Score
A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.
epss
0.25 / 0.5
No EPSS data
freshness
1.00 / 1.0
6d stale
scorecard
3.12 / 4.0
Score 7.8/10
cve health
0.00 / 2.5
No open CVEs
patch speed
0.50 / 0.5
⚠ Estimated — no CVE patch history
kev exposure
1.50 / 1.5
No KEV exposure
supply chain risk
-1.50 / 10.0
Risk 26.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
7.4
10%
Provenance trust
provenance trust
7.8
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
8.5
10%
How is this calculated?
The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.
Supply Chain Risk
Risk 26.0/100Scorecard
Scorecard 7.8/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 10 | all changesets reviewed |
| Maintained | 10 | 30 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10 |
| Security-Policy | 10 | security policy file detected |
| Packaging | -1 | packaging workflow not detected |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| CII-Best-Practices | 5 | badge detected: Passing |
| Token-Permissions | 9 | detected GitHub workflow tokens with excessive permissions |
| License | 10 | license file detected |
| Fuzzing | 10 | project is fuzzed |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Branch-Protection | 4 | branch protection is not maximal on development and all release branches |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| SAST | 9 | SAST tool is not run on all commits -- score normalized to 9 |
| Pinned-Dependencies | 3 | dependency not pinned by hash detected -- score normalized to 3 |
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
0
High
0
Medium
0
Low
0
Unknown
1
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-33814 | unknown | — | golang.org/x/net | v0.52.0 | — |
Showing 1 of 17