Security Deep Dive
OmniPoly
Security posture and CVE patch evidence from tracked releases.
1 actively-exploited dependency CVE affects v0.16.0.
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.97 / 1.0
40d stale
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
0.25 / 2.5
⚠ No direct scan — 0c/10h 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 36.1/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
1.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
6.4
10%
Provenance trust
provenance trust
5.0
40%
Maintainer health
maintainer health
9.7
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 36.1/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
0
High
10
Medium
21
Low
4
Unknown
0
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-26996 | high | — | minimatch | 9.0.4 | — |
| CVE-2026-27606 | high | — | rollup | 4.34.7 | — |
| CVE-2026-27903 | high | — | minimatch | 9.0.4 | — |
| CVE-2026-27904 | high | — | minimatch | 9.0.4 | — |
| CVE-2026-32141 | high | — | flatted | 3.3.1 | — |
| CVE-2026-33228 | high | — | flatted | 3.3.1 | — |
| CVE-2026-33671 | high | — | picomatch | 2.3.1 | — |
| CVE-2026-39363 | high | — | vite | 6.1.0 | — |
| CVE-2026-4800 | high | — | lodash | 4.17.21 | — |
| CVE-2026-4867 | high | — | path-to-regexp | 0.1.12 | — |
| CVE-2025-13465 | medium | — | lodash | 4.17.21 | — |
| CVE-2025-15284 | medium | — | qs | 6.13.0 | — |
| CVE-2025-27789 | medium | — | @babel/runtime | 7.24.7 | — |
| CVE-2025-30208 | medium | — | vite | 6.1.0 | — |
| CVE-2025-31125 | medium | KEV | vite | 6.1.0 | — |
| CVE-2025-31486 | medium | — | vite | 6.1.0 | — |
| CVE-2025-32395 | medium | — | vite | 6.1.0 | — |
| CVE-2025-32996 | medium | — | http-proxy-middleware | 3.0.3 | — |
| CVE-2025-32997 | medium | — | http-proxy-middleware | 3.0.3 | — |
| CVE-2025-46565 | medium | — | vite | 6.1.0 | — |
| CVE-2025-62522 | medium | — | vite | 6.1.0 | — |
| CVE-2025-64718 | medium | — | js-yaml | 3.14.1 | — |
| CVE-2025-69873 | medium | — | ajv | 6.12.6 | — |
| CVE-2026-2950 | medium | — | lodash | 4.17.21 | — |
| CVE-2026-33532 | medium | — | yaml | 1.10.2 | — |
| CVE-2026-33672 | medium | — | picomatch | 2.3.1 | — |
| CVE-2026-33750 | medium | — | brace-expansion | 1.1.11 | — |
| CVE-2026-39365 | medium | — | vite | 6.1.0 | — |
| CVE-2026-41305 | medium | — | postcss | 8.4.38 | — |
| GHSA-67mh-4wv8-2f99 | medium | — | esbuild | 0.24.2 | — |
| GHSA-r4q5-vmmm-2653 | medium | — | follow-redirects | 1.15.9 | — |
| CVE-2025-58751 | low | — | vite | 6.1.0 | — |
| CVE-2025-58752 | low | — | vite | 6.1.0 | — |
| CVE-2025-5889 | low | — | brace-expansion | 1.1.11 | — |
| CVE-2026-2391 | low | — | qs | 6.13.0 | — |
Showing 35 of 35