Security Deep Dive
WatchYourLAN
Security posture and CVE patch evidence from tracked releases.
1 actively-exploited dependency CVE affects 2.1.4.
KEV-listed CVEs are confirmed exploited in the wild — patch urgently.
Trust Signals — 2 of 9 Present
Evidence already collected from releases and repository metadata.
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.30 / 1.0
265d stale
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
0.00 / 2.5
⚠ No direct scan — 1c/7h 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 33.6/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
6.6
10%
Provenance trust
provenance trust
5.0
40%
Maintainer health
maintainer health
3.0
10%
Operational risk
operational risk
8.5
10%
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 33.6/100OpenSSF Badge
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
1
High
7
Medium
10
Low
3
Unknown
5
1 dependency vulnerabilities are in KEV.
CISA confirmed these vulnerabilities are actively exploited. Treat as critical priority.
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-33816 | critical | — | github.com/jackc/pgx/v5 | 5.6.0 | — |
| CVE-2026-23736 | high | — | seroval | 1.2.1 | — |
| CVE-2026-23737 | high | — | seroval | 1.2.1 | — |
| CVE-2026-23956 | high | — | seroval | 1.2.1 | — |
| CVE-2026-23957 | high | — | seroval | 1.2.1 | — |
| CVE-2026-24006 | high | — | seroval | 1.2.1 | — |
| CVE-2026-27606 | high | — | rollup | 4.35.0 | — |
| CVE-2026-39363 | high | — | vite | 6.2.2 | — |
| CVE-2025-30208 | medium | — | vite | 6.2.2 | — |
| CVE-2025-31125 | medium | KEV | vite | 6.2.2 | — |
| CVE-2025-31486 | medium | — | vite | 6.2.2 | — |
| CVE-2025-32395 | medium | — | vite | 6.2.2 | — |
| CVE-2025-46565 | medium | — | vite | 6.2.2 | — |
| CVE-2025-47914 | medium | — | golang.org/x/crypto | 0.41.0 | — |
| CVE-2025-58181 | medium | — | golang.org/x/crypto | 0.41.0 | — |
| CVE-2025-62522 | medium | — | vite | 6.2.2 | — |
| CVE-2026-39365 | medium | — | vite | 6.2.2 | — |
| CVE-2026-41305 | medium | — | postcss | 8.5.3 | — |
| CVE-2025-58751 | low | — | vite | 6.2.2 | — |
| CVE-2025-58752 | low | — | vite | 6.2.2 | — |
| CVE-2026-41889 | low | — | github.com/jackc/pgx/v5 | 5.6.0 | — |
| CVE-2025-47911 | unknown | — | golang.org/x/net | 0.43.0 | — |
| CVE-2025-47913 | unknown | — | golang.org/x/crypto | 0.41.0 | — |
| CVE-2025-58190 | unknown | — | golang.org/x/net | 0.43.0 | — |
| CVE-2026-33814 | unknown | — | golang.org/x/net | 0.43.0 | — |
| CVE-2026-33815 | unknown | — | github.com/jackc/pgx/v5 | 5.6.0 | — |
Showing 26 of 26