Tools / tracktor / Security

Security Deep Dive

tracktor

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 high-severity dependency CVEs affects 1.4.0.

Review the dependency vulnerabilities below.

— Signed — SLSA ✓ SBOM ✗ Security policy Monthly cadence · 33d 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 Present

GitHub SBOM API Latest release

Last verified: 28d ago

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 17d ago

Release cadence: monthly Present

33d median over recent releases Release history

Latest release: 2mo ago

Maintainer active Present

Recent commit activity Repository

Last commit: 20d 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

6.8/10 Security Score

Dependency Exposure 10 transitive dependency CVEs found in the latest SBOM.

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

20d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

2.00 / 2.5

No open 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.48 / 10.0

Risk 4.8/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

8.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

9.5

10%

supply chain risk: 4.83 transitive cves: 0c/2h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 20d

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.8/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

58% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

734 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 (10) All (10)

High 2 Medium 7 Low 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-33671	high	—	picomatch	4.0.3	—
CVE-2026-4800	high	—	lodash-es	4.17.23	—
CVE-2026-2950	medium	—	lodash-es	4.17.23	—
CVE-2026-33532	medium	—	yaml	1.10.2	—
CVE-2026-33672	medium	—	picomatch	4.0.3	—
CVE-2026-33750	medium	—	brace-expansion	5.0.4	—
CVE-2026-41305	medium	—	postcss	8.5.8	—
CVE-2026-41907	medium	—	uuid	13.0.0	—
GHSA-67mh-4wv8-2f99	medium	—	esbuild	0.18.20	—
CVE-2024-47764	low	—	cookie	0.6.0	—

Showing 10 of 10