Skip to content

Security Deep Dive

kustomize-controller

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against v1.8.5.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 13d median Active maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/9 Present
Signed releases Unknown
Latest release artifact signature Latest release
SLSA provenance Unknown
Attestation predicate level Latest release
SBOM published Unknown
GitHub SBOM API Latest release
SECURITY.md Absent
GitHub repository metadata Repository policy
Checked: 22d ago
Release cadence: weekly Present
13d median over recent releases Release history
Latest release: 22d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 6d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 22d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 22d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 22d ago
7.7/10 Security Score
8.1/10 Scorecard

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.24 / 4.0

Score 8.1/10

cve health

1.25 / 2.5

⚠ Estimated — no scan yet

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

0.00 / 10.0

Risk 0.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

5.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

10.0

10%

supply chain risk: 0.0 transitive cves: 0c/0h

Provenance trust

provenance trust

8.1

40%

scorecard score: 8.1 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 6d

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.

Scorecard

Scorecard 8.1/10

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

Check Score Reason
Code-Review 10 all changesets reviewed
Binary-Artifacts 10 no binaries found in the repo
Dangerous-Workflow 10 no dangerous workflow patterns detected
Packaging -1 packaging workflow not detected
Maintained 10 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
CII-Best-Practices 5 badge detected: Passing
Fuzzing 10 project is fuzzed
License 10 license file detected
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
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0
Security-Policy 10 security policy file detected
Signed-Releases 10 5 out of the last 5 releases have a total of 10 signed artifacts.
SAST 10 SAST tool is run on all commits

Beta — feedback welcome: [email protected]