Tools / Watcharr / Security

Security Deep Dive

Watcharr

Security posture and CVE patch evidence from tracked releases.

Back to Tool

16 high-severity dependency CVEs affects v4.1.1.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 5d 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: 14d ago

Release cadence: weekly Present

5d median over recent releases Release history

Latest release: 1d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 8d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 1d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 1d ago

Signing assets Not active yet

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

Latest release: 1d ago

3.8/10 Security Score

Dependency Exposure 40 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

Up to date

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

0.00 / 2.5

⚠ No direct scan — 1c/27h 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

-1.50 / 10.0

Risk 59.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

4.1

10%

supply chain risk: 59.04 transitive cves: 1c/27h

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

48% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1802 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 (40) All (73)

High 16 Medium 17 Low 3 Unknown 4

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2025-58754	high	—	axios	1.9.0	v4.0.0
CVE-2025-59530	high	—	github.com/quic-go/quic-go	v0.54.0	v4.0.0
CVE-2025-67647	high	—	@sveltejs/kit	2.21.0	v4.0.0
CVE-2026-25639	high	—	axios	1.9.0	v4.0.0
CVE-2026-27606	high	—	rollup	2.79.2	v4.0.0
CVE-2026-29074	high	—	svgo	3.3.2	v4.0.0
CVE-2026-32141	high	—	flatted	3.3.2	v4.0.0
CVE-2026-33228	high	—	flatted	3.3.2	v4.0.0
CVE-2026-40073	high	—	@sveltejs/kit	2.21.0	v4.0.0
CVE-2026-42033	high	—	axios	1.9.0	v4.0.0
CVE-2026-42035	high	—	axios	1.9.0	v4.0.0
CVE-2026-42043	high	—	axios	1.9.0	v4.0.0
CVE-2026-42264	high	—	axios	1.9.0	v4.0.0
CVE-2026-4867	high	—	path-to-regexp	0.1.12	v4.0.0
CVE-2026-6321	high	—	fast-uri	3.0.3	v4.0.0
CVE-2026-6322	high	—	fast-uri	3.0.3	v4.0.0
CVE-2025-47914	medium	—	golang.org/x/crypto	v0.40.0	v4.0.0
CVE-2025-58181	medium	—	golang.org/x/crypto	v0.40.0	v4.0.0
CVE-2025-62718	medium	—	axios	1.9.0	v4.0.0
CVE-2025-64702	medium	—	github.com/quic-go/quic-go	v0.54.0	v4.0.0
CVE-2026-33532	medium	—	yaml	1.10.2	v4.0.0
CVE-2026-33750	medium	—	brace-expansion	1.1.11	v4.0.0
CVE-2026-40074	medium	—	@sveltejs/kit	2.21.0	v4.0.0
CVE-2026-40175	medium	—	axios	1.9.0	v4.0.0
CVE-2026-42034	medium	—	axios	1.9.0	v4.0.0
CVE-2026-42036	medium	—	axios	1.9.0	v4.0.0
CVE-2026-42037	medium	—	axios	1.9.0	v4.0.0
CVE-2026-42038	medium	—	axios	1.9.0	v4.0.0
CVE-2026-42039	medium	—	axios	1.9.0	v4.0.0
CVE-2026-42041	medium	—	axios	1.9.0	v4.0.0
CVE-2026-42042	medium	—	axios	1.9.0	v4.0.0
CVE-2026-42044	medium	—	axios	1.9.0	v4.0.0
GHSA-r4q5-vmmm-2653	medium	—	follow-redirects	1.15.9	v4.0.0
CVE-2024-47764	low	—	cookie	0.6.0	v4.0.0
CVE-2025-5889	low	—	brace-expansion	1.1.11	v4.0.0
CVE-2026-42040	low	—	axios	1.9.0	v4.0.0
CVE-2025-47911	unknown	—	golang.org/x/net	v0.42.0	v4.0.0
CVE-2025-47913	unknown	—	golang.org/x/crypto	v0.40.0	v4.0.0
CVE-2025-58190	unknown	—	golang.org/x/net	v0.42.0	v4.0.0
CVE-2026-33814	unknown	—	golang.org/x/net	v0.42.0	v4.0.0

Showing 40 of 73