Skip to content
Tools / bugsink / Security

Security Deep Dive

bugsink

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No known vulnerabilities in 2.2.1.

2 CVEs patched in tracked history. Median patch time: 0 days.

Versions by Severity

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

13 versions tracked
Version Published C H M L KEV Notes
2.2.1 2026-05-22
Latest
2.2.0 2026-05-21
2.1.3 2026-05-02
2.1.2 2026-04-11
2.1.1 2026-04-09
2.1.0 2026-04-04 1
2.0.14 2026-03-03 1
2.0.13 2026-02-21 1
2.0.12 2026-01-26 1 1
2.0.11 2026-01-20 1 1
2.0.9 2026-01-13 1 1
2.0.8 2026-01-10 1 1
2.0.7 2026-01-10 1 1
— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 6d 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
6d median over recent releases Release history
Latest release: 12d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 1d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 12d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 12d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 12d ago
3.8/10 Security Score
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

Up to date

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

0.00 / 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

-1.50 / 10.0

Risk 100.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: 0

Dependency exposure

dependency exposure

0.0

10%

supply chain risk: 100.0 transitive cves: 17c/76h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated 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.

Supply Chain Risk

Risk 100.0/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
59% Dependency freshness

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
2
CVE Severity EPSS Disclosed Fixed in Days to fix vs Ecosystem Median KEV
GHSA-8hw4-fhww-273g High 2.1.1
GHSA-vp6q-7m36-pq3w Critical 2.0.13

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

Dependency Vulnerabilities

151 dependencies scanned View full dependency list →

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

0

No dependency CVEs match this filter.

Showing 0 of 175

Beta — feedback welcome: [email protected]