Skip to content
Tools / Beets / Security

Security Deep Dive

Beets

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No known vulnerabilities in v2.11.0.

1 CVE patched in tracked history. Median patch time: 0 days.

Versions by Severity

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

9 versions tracked
Version Published C H M L KEV Notes
v2.11.0 2026-05-06
Latest
v2.10.0 2026-04-19
v2.9.0 2026-04-11
v2.8.0 2026-03-28
v2.7.1 2026-03-08
v2.7.0 2026-03-07
v2.6.2 2026-02-22
v2.6.1 2026-02-02
v2.6.0 2026-02-01
— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 13d median 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 Unknown
GitHub SBOM API Latest release
SECURITY.md Present
GitHub repository metadata Repository policy
Checked: 22d ago
Release cadence: weekly Present
13d median over recent releases Release history
Latest release: 28d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 1d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 28d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 28d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 28d ago
8.0/10 Security Score
5.6/10 Scorecard
0d avg CVE Patch Speed

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

1d stale

scorecard

2.24 / 4.0

Score 5.6/10

cve health

2.50 / 2.5

No open CVEs

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

10.0

25%

direct cves: clear 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

5.6

40%

scorecard score: 5.6 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

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 5.6/10

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

Check Score Reason
Code-Review 7 Found 5/7 approved changesets -- score normalized to 7
Maintained 10 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow 10 no dangerous workflow patterns detected
Security-Policy 10 security policy file detected
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts 10 no binaries found in the repo
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0
Fuzzing 0 project is not fuzzed
License 10 license file detected
Packaging 10 packaging workflow detected
Branch-Protection 5 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 3 SAST tool is not run on all commits -- score normalized to 3

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

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
1
CVE Severity EPSS Disclosed Fixed in Days to fix vs Ecosystem Median KEV
GHSA-3gxm-wfjx-m847 unknown v2.10.0

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

Beta — feedback welcome: [email protected]