Skip to content
Tools / cloud-init / Security

Security Deep Dive

cloud-init

Security posture and CVE patch evidence from tracked releases.

Back to Tool

4 critical dependency CVEs affects 26.1.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA ✓ SBOM ✓ Security policy Unknown cadence Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present
Signed releases Unknown
Latest release artifact signature Latest release
SLSA provenance Unknown
Attestation predicate level Latest release
SBOM published Present
GitHub SBOM API Latest release
Last verified: 28d ago
SECURITY.md Present
GitHub repository metadata Repository policy
Checked: 18d ago
Release cadence Unknown
12-release median Release history
Latest release: 3mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: 28d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 3mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 3mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 3mo ago
4.2/10 Security Score
6.0/10 Scorecard
Pending CVE Patch Speed
Open CVEs Open CVEs detected for latest version.

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

28d stale

scorecard

2.40 / 4.0

Score 6.0/10

cve health

0.00 / 2.5

Open CVEs detected

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 24.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: open cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

7.6

10%

supply chain risk: 24.0 transitive cves: 4c/4h

Provenance trust

provenance trust

6.0

40%

scorecard score: 6.0 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 28d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none
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 24.0/100
4 Transitive critical CVEs
0 KEV-transitive CVEs
100% Dependency freshness

Scorecard

Scorecard 6.0/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check Score Reason
Security-Policy 10 security policy file detected
Maintained 10 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Code-Review 10 all changesets reviewed
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Packaging -1 packaging workflow not detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
Binary-Artifacts 10 no binaries found in the repo
Pinned-Dependencies 7 dependency not pinned by hash detected -- score normalized to 7
License 9 license file detected
Fuzzing 0 project is not fuzzed
Branch-Protection -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Signed-Releases 0 Project has not signed or included provenance with any releases.
SAST 0 SAST tool is not run on all commits -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

43 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

4

High

4

Medium

16

Low

1

Unknown

0

Critical 4 High 4 Medium 16 Low 1
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2017-18342 critical pyyaml
CVE-2019-20477 critical pyyaml
CVE-2020-14343 critical pyyaml
CVE-2020-1747 critical pyyaml
CVE-2014-1402 high jinja2
CVE-2016-10745 high jinja2
CVE-2018-18074 high requests
CVE-2019-10906 high jinja2
CVE-2014-0012 medium jinja2
CVE-2014-1829 medium requests
CVE-2014-1830 medium requests
CVE-2015-2296 medium requests
CVE-2020-28493 medium jinja2
CVE-2022-36087 medium oauthlib
CVE-2023-32681 medium requests
CVE-2024-22195 medium jinja2
CVE-2024-34064 medium jinja2
CVE-2024-35195 medium requests
CVE-2024-47081 medium requests
CVE-2024-56201 medium jinja2
CVE-2024-56326 medium jinja2
CVE-2025-27516 medium jinja2
CVE-2025-71176 medium pytest
CVE-2026-25645 medium requests
CVE-2023-26112 low configobj

Showing 25 of 25

Beta — feedback welcome: [email protected]