Security Deep Dive
grr
Security posture and CVE patch evidence from tracked releases.
48 high-severity dependency CVEs affects v.4.0.0.0-release.
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
21d stale
scorecard
1.96 / 4.0
Score 4.9/10
cve health
1.50 / 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 100.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
6.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
0.0
10%
Provenance trust
provenance trust
4.9
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 100.0/100Scorecard
Scorecard 4.9/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 7 | Found 21/30 approved changesets -- score normalized to 7 |
| Maintained | 2 | 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| License | 10 | license file detected |
| Signed-Releases | -1 | no releases found |
| Binary-Artifacts | 5 | binaries present in source code |
| Security-Policy | 10 | security policy file detected |
| Branch-Protection | -1 | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| Fuzzing | 0 | project is not fuzzed |
| Packaging | 10 | packaging workflow detected |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| SAST | 3 | SAST tool is not run on all commits -- score normalized to 3 |
OpenSSF 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
48
Medium
30
Low
8
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2022-21680 | high | — | marked | 0.7.0 | — |
| CVE-2022-21681 | high | — | marked | 0.7.0 | — |
| CVE-2022-21699 | high | — | ipython | 7.15.0 | — |
| CVE-2022-28108 | high | — | selenium | 3.141.0 | — |
| CVE-2023-25577 | high | — | werkzeug | 2.1.2 | — |
| CVE-2023-5590 | high | — | selenium | 3.141.0 | — |
| CVE-2024-34069 | high | — | werkzeug | 2.1.2 | — |
| CVE-2024-6345 | high | — | setuptools | 69.5.1 | — |
| CVE-2025-12816 | high | — | node-forge | 1.3.1 | — |
| CVE-2025-47273 | high | — | setuptools | 69.5.1 | — |
| CVE-2025-59042 | high | — | pyinstaller | 5.13.2 | — |
| CVE-2025-64756 | high | — | glob | 10.4.5 | — |
| CVE-2025-66031 | high | — | node-forge | 1.3.1 | — |
| CVE-2025-66035 | high | — | @angular/common | 19.2.15 | — |
| CVE-2025-66412 | high | — | @angular/compiler | 9.0.0 | — |
| CVE-2026-22610 | high | — | @angular/core | 19.2.15 | — |
| CVE-2026-22610 | high | — | @angular/compiler | 9.0.0 | — |
| CVE-2026-23745 | high | — | tar | 6.2.1 | — |
| CVE-2026-23950 | high | — | tar | 6.2.1 | — |
| CVE-2026-24049 | high | — | wheel | 0.43.0 | — |
| CVE-2026-24842 | high | — | tar | 6.2.1 | — |
| CVE-2026-26960 | high | — | tar | 6.2.1 | — |
| CVE-2026-26996 | high | — | minimatch | 3.1.2 | — |
| CVE-2026-27606 | high | — | rollup | 4.53.2 | — |
| CVE-2026-27903 | high | — | minimatch | 3.1.2 | — |
| CVE-2026-27904 | high | — | minimatch | 3.1.2 | — |
| CVE-2026-27970 | high | — | @angular/core | 19.2.15 | — |
| CVE-2026-29063 | high | — | immutable | 5.1.4 | — |
| CVE-2026-29786 | high | — | tar | 6.2.1 | — |
| CVE-2026-31802 | high | — | tar | 6.2.1 | — |
| CVE-2026-32141 | high | — | flatted | 3.3.3 | — |
| CVE-2026-32597 | high | — | pyjwt | 2.6.0 | — |
| CVE-2026-32635 | high | — | @angular/compiler | 19.2.15 | — |
| CVE-2026-32635 | high | — | @angular/core | 19.2.15 | — |
| CVE-2026-33151 | high | — | socket.io-parser | 4.2.4 | — |
| CVE-2026-33228 | high | — | flatted | 3.3.3 | — |
| CVE-2026-33671 | high | — | picomatch | 2.3.1 | — |
| CVE-2026-33891 | high | — | node-forge | 1.3.1 | — |
| CVE-2026-33894 | high | — | node-forge | 1.3.1 | — |
| CVE-2026-33895 | high | — | node-forge | 1.3.1 | — |
| CVE-2026-33896 | high | — | node-forge | 1.3.1 | — |
| CVE-2026-39363 | high | — | vite | 6.4.1 | — |
| CVE-2026-4800 | high | — | lodash | 4.17.21 | — |
| CVE-2026-4867 | high | — | path-to-regexp | 0.1.12 | — |
| CVE-2026-6321 | high | — | fast-uri | 3.1.0 | — |
| CVE-2026-6322 | high | — | fast-uri | 3.1.0 | — |
| GHSA-36jr-mh4h-2g58 | high | — | d3-color | 1.4.1 | — |
| GHSA-5c6j-r48x-rmvq | high | — | serialize-javascript | 6.0.2 | — |
| CVE-2021-4231 | medium | — | @angular/core | 9.0.0 | — |
| CVE-2023-32681 | medium | — | requests | 2.25.1 | — |
| CVE-2023-46136 | medium | — | werkzeug | 2.1.2 | — |
| CVE-2024-22195 | medium | — | jinja2 | 3.1.2 | — |
| CVE-2024-34064 | medium | — | jinja2 | 3.1.2 | — |
| CVE-2024-49766 | medium | — | werkzeug | 2.1.2 | — |
| CVE-2024-49767 | medium | — | werkzeug | 2.1.2 | — |
| CVE-2024-56201 | medium | — | jinja2 | 3.1.2 | — |
| CVE-2024-56326 | medium | — | jinja2 | 3.1.2 | — |
| CVE-2025-13465 | medium | — | lodash | 4.17.21 | — |
| CVE-2025-15284 | medium | — | qs | 6.13.0 | — |
| CVE-2025-27516 | medium | — | jinja2 | 3.1.2 | — |
| CVE-2025-64718 | medium | — | js-yaml | 4.1.0 | — |
| CVE-2025-66030 | medium | — | node-forge | 1.3.1 | — |
| CVE-2025-66221 | medium | — | werkzeug | 2.1.2 | — |
| CVE-2025-69873 | medium | — | ajv | 8.17.1 | — |
| CVE-2025-71176 | medium | — | pytest | 7.2.1 | — |
| CVE-2025-8869 | medium | — | pip | 24.0 | — |
| CVE-2026-21860 | medium | — | werkzeug | 2.1.2 | — |
| CVE-2026-27199 | medium | — | werkzeug | 2.1.2 | — |
| CVE-2026-2950 | medium | — | lodash | 4.17.21 | — |
| CVE-2026-3219 | medium | — | pip | 24.0 | — |
| CVE-2026-33672 | medium | — | picomatch | 2.3.1 | — |
| CVE-2026-33750 | medium | — | brace-expansion | 1.1.12 | — |
| CVE-2026-34043 | medium | — | serialize-javascript | 6.0.2 | — |
| CVE-2026-39365 | medium | — | vite | 6.4.1 | — |
| CVE-2026-41305 | medium | — | postcss | 8.5.6 | — |
| CVE-2026-42338 | medium | — | ip-address | 10.1.0 | — |
| CVE-2026-6357 | medium | — | pip | 24.0 | — |
| GHSA-r4q5-vmmm-2653 | medium | — | follow-redirects | 1.15.11 | — |
| CVE-2023-23934 | low | — | werkzeug | 2.1.2 | — |
| CVE-2023-24816 | low | — | ipython | 7.15.0 | — |
| CVE-2025-68157 | low | — | webpack | 5.98.0 | — |
| CVE-2025-68458 | low | — | webpack | 5.98.0 | — |
| CVE-2026-1703 | low | — | pip | 24.0 | — |
| CVE-2026-2391 | low | — | qs | 6.13.0 | — |
| CVE-2026-24001 | low | — | diff | 4.0.2 | — |
| CVE-2026-27448 | low | — | pyopenssl | 21.0.0 | — |
Showing 86 of 109