Security Deep Dive
ontime
Security posture and CVE patch evidence from tracked releases.
15 high-severity dependency CVEs affects v4.8.0.
Review the dependency vulnerabilities below.
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
1.00 / 1.0
6d stale
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
1.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
-1.50 / 10.0
Risk 77.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
4.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
2.3
10%
Provenance trust
provenance trust
5.0
40%
Maintainer health
maintainer health
10.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 77.0/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
15
Medium
14
Low
3
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2023-30533 | high | — | xlsx | 0.18.5 | v4.8.0 |
| CVE-2024-22363 | high | — | xlsx | 0.18.5 | v4.8.0 |
| CVE-2025-65945 | high | — | jws | 4.0.0 | v4.8.0 |
| CVE-2026-25639 | high | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-33671 | high | — | picomatch | 2.3.1 | v4.8.0 |
| CVE-2026-34601 | high | — | @xmldom/xmldom | 0.8.11 | v4.8.0 |
| CVE-2026-3520 | high | — | multer | 2.1.0 | v4.8.0 |
| CVE-2026-41672 | high | — | @xmldom/xmldom | 0.8.11 | v4.8.0 |
| CVE-2026-41673 | high | — | @xmldom/xmldom | 0.8.11 | v4.8.0 |
| CVE-2026-41674 | high | — | @xmldom/xmldom | 0.8.11 | v4.8.0 |
| CVE-2026-41675 | high | — | @xmldom/xmldom | 0.8.11 | v4.8.0 |
| CVE-2026-42033 | high | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42035 | high | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42043 | high | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42264 | high | — | axios | 1.12.2 | v4.8.0 |
| CVE-2025-13466 | medium | — | body-parser | 2.2.0 | v4.8.0 |
| CVE-2025-62718 | medium | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-33672 | medium | — | picomatch | 2.3.1 | v4.8.0 |
| CVE-2026-40175 | medium | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42034 | medium | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42036 | medium | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42037 | medium | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42038 | medium | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42039 | medium | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42041 | medium | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42042 | medium | — | axios | 1.12.2 | v4.8.0 |
| CVE-2026-42044 | medium | — | axios | 1.12.2 | v4.8.0 |
| GHSA-67mh-4wv8-2f99 | medium | — | esbuild | 0.24.2 | v4.8.0 |
| GHSA-r4q5-vmmm-2653 | medium | — | follow-redirects | 1.15.6 | v4.8.0 |
| CVE-2025-7339 | low | — | on-headers | 1.0.2 | v4.8.0 |
| CVE-2026-3449 | low | — | @tootallnate/once | 2.0.0 | v4.8.0 |
| CVE-2026-42040 | low | — | axios | 1.12.2 | v4.8.0 |
Showing 32 of 78