Tools / poenskelisten / Security

Security Deep Dive

poenskelisten

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v2.3.0.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA ✓ SBOM ✗ Security policy Unknown cadence Sporadic 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 Present

GitHub SBOM API Latest release

Last verified: 28d ago

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 18d ago

Release cadence Unknown

12-release median Release history

Latest release: 2mo ago

Maintainer sporadic Present

Recent commit activity Repository

Last commit: 1mo ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 2mo ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 2mo ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 2mo ago

5.6/10 Security Score

Dependency Exposure 4 transitive dependency CVEs found in the latest SBOM. 1 critical.

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

0.96 / 1.0

42d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

0.75 / 2.5

⚠ No direct scan — 1c/0h transitive CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-0.40 / 10.0

Risk 4.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

3.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

9.6

10%

supply chain risk: 4.0 transitive cves: 1c/0h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

9.6

10%

activity freshness: 42d

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

1 Transitive critical CVEs

0 KEV-transitive CVEs

100% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

75 dependencies scanned View full dependency list →

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

Critical

High

Medium

Low

Unknown

Still affecting latest (4) All (4)

Critical 1 Low 1 Unknown 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-33816	critical	—	github.com/jackc/pgx/v5	v5.8.0	—
CVE-2026-41889	low	—	github.com/jackc/pgx/v5	v5.8.0	—
CVE-2026-33814	unknown	—	golang.org/x/net	v0.52.0	—
CVE-2026-33815	unknown	—	github.com/jackc/pgx/v5	v5.8.0	—

Showing 4 of 4