Skip to content
Tools / pipeline / Security

Security Deep Dive

pipeline

Security posture and CVE patch evidence from tracked releases.

Back to Tool

Open CVEs reported against v1.13.0.

See the CVE patch history below for context.

Versions by Severity

CVEs are attributed to tracked releases published before the patch release.

20 versions tracked
Version Published C H M L KEV Notes
v1.13.0 2026-05-29
Latest
v1.12.0 2026-05-04
v1.11.1 2026-04-21
v1.9.3 2026-04-21 2
v1.6.2 2026-04-21 4
v1.3.4 2026-04-21 6
v1.0.2 2026-04-21 8
v1.11.0 2026-03-30 10
v1.10.2 2026-03-18 10
v1.9.2 2026-03-18 1 10
v1.6.1 2026-03-18 2 10
v1.3.3 2026-03-18 3 10
v1.0.1 2026-03-18 4 10
v1.10.1 2026-03-12 5 10
v1.10.0 2026-02-27 5 10
v1.9.1 2026-02-19 5 10
v1.9.0 2026-01-30 5 10
v1.7.0 2025-12-03 5 10
v1.6.0 2025-10-31 5 10
v1.5.0 2025-10-02 5 10
— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 0d 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
0d median over recent releases Release history
Latest release: 5d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 1d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 5d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 5d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 5d ago
5.8/10 Security Score
6.5/10 Scorecard
0d avg CVE Patch Speed
Open CVEs Open CVEs detected for latest version.
Patch speed: 0d

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

Up to date

scorecard

2.60 / 4.0

Score 6.5/10

cve health

0.00 / 2.5

Open CVEs detected

patch speed

0.50 / 0.5

0d avg

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

0.0

25%

direct cves: open cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: 0

Dependency exposure

dependency exposure

10.0

10%

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

Provenance trust

provenance trust

6.5

40%

scorecard score: 6.5 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 0d

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 6.5/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
Maintained 10 30 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow 10 no dangerous workflow patterns detected
Dependency-Update-Tool 10 update tool detected
Packaging -1 packaging workflow not detected
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
CII-Best-Practices 5 badge detected: Passing
Binary-Artifacts 10 no binaries found in the repo
Signed-Releases 0 Project has not signed or included provenance with any releases.
License 10 license file detected
Pinned-Dependencies 8 dependency not pinned by hash detected -- score normalized to 8
Branch-Protection 3 branch protection is not maximal on development and all release branches
SAST 10 SAST tool is run on all commits
Fuzzing 0 project is not fuzzed
Vulnerabilities 0 25 existing vulnerabilities detected
Security-Policy 10 security policy file detected
CI-Tests 10 26 out of 26 merged PRs checked by a CI test -- score normalized to 10
Contributors 10 project has 52 contributing companies or organizations

CVE Patch History

Median patch time: 0 days

Tracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.

CVEs Patched by Year

Critical High Medium Low
2026
28
CVE Severity EPSS Disclosed Fixed in Days to fix vs Ecosystem Median KEV
GHSA-94jr-7pqp-xhcq High v1.11.1
GHSA-m2cx-gpqf-qf74 unknown v1.11.1
GHSA-rx35-6rhx-7858 unknown v1.11.1
GHSA-wjxp-xrpv-xpff High v1.11.1
GHSA-94jr-7pqp-xhcq High v1.9.3
GHSA-wjxp-xrpv-xpff High v1.9.3
GHSA-94jr-7pqp-xhcq High v1.6.2
GHSA-wjxp-xrpv-xpff High v1.6.2
GHSA-94jr-7pqp-xhcq High v1.3.4
GHSA-wjxp-xrpv-xpff High v1.3.4
GHSA-94jr-7pqp-xhcq High v1.0.2
GHSA-wjxp-xrpv-xpff High v1.0.2
GHSA-rmx9-2pp3-xhcr unknown v1.11.0
GHSA-cv4x-93xx-wgfj unknown v1.10.2
GHSA-j5q5-j9gm-2w5c Critical v1.10.2
GO-2026-4761 unknown v1.10.2
GHSA-cv4x-93xx-wgfj unknown v1.9.2
GHSA-j5q5-j9gm-2w5c Critical v1.9.2
GO-2026-4761 unknown v1.9.2
GHSA-cv4x-93xx-wgfj unknown v1.6.1
GHSA-j5q5-j9gm-2w5c Critical v1.6.1
GO-2026-4761 unknown v1.6.1
GHSA-cv4x-93xx-wgfj unknown v1.3.3
GHSA-j5q5-j9gm-2w5c Critical v1.3.3
GO-2026-4761 unknown v1.3.3
GHSA-cv4x-93xx-wgfj unknown v1.0.1
GHSA-j5q5-j9gm-2w5c Critical v1.0.1
GO-2026-4761 unknown v1.0.1

KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.

Beta — feedback welcome: [email protected]