Security Deep Dive
Vagrant
Security posture and CVE patch evidence from tracked releases.
4 critical dependency CVEs affects v2.4.9.
Audit transitive dependencies; consider upgrading or pinning replacements.
Trust Signals — 3 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
2d stale
scorecard
2.16 / 4.0
Score 5.4/10
cve health
0.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 53.2/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
4.7
10%
Provenance trust
provenance trust
5.4
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 53.2/100Scorecard
Scorecard 5.4/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 3 | Found 4/12 approved changesets -- score normalized to 3 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Maintained | 4 | 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4 |
| Packaging | -1 | packaging workflow not detected |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Pinned-Dependencies | 6 | dependency not pinned by hash detected -- score normalized to 6 |
| Fuzzing | 0 | project is not fuzzed |
| License | 9 | license file detected |
| Signed-Releases | 8 | 5 out of the last 5 releases have a total of 5 signed artifacts. |
| 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 |
| Security-Policy | 10 | security policy file detected |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
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
4
High
18
Medium
28
Low
6
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2022-29078 | critical | — | ejs | 3.1.5 | — |
| CVE-2023-45133 | critical | — | @babel/traverse | 7.21.2 | — |
| CVE-2025-29927 | critical | — | next | 12.3.1 | — |
| CVE-2025-7783 | critical | — | form-data | 3.0.1 | — |
| CVE-2020-7661 | high | — | url-regex | 5.0.0 | — |
| CVE-2020-7753 | high | — | trim | 0.0.1 | — |
| CVE-2021-28965 | high | — | rexml | 3.2 | — |
| CVE-2022-25883 | high | — | semver | 6.3.0 | — |
| CVE-2023-2251 | high | — | yaml | 2.2.1 | — |
| CVE-2024-21538 | high | — | cross-spawn | 6.0.5 | — |
| CVE-2024-37890 | high | — | ws | 7.5.7 | — |
| CVE-2024-4068 | high | — | braces | 2.3.2 | — |
| CVE-2024-43398 | high | — | rexml | 3.2 | — |
| CVE-2024-47220 | high | — | webrick | 1.7 | — |
| CVE-2024-51479 | high | — | next | 12.3.1 | — |
| CVE-2026-26996 | high | — | minimatch | 3.1.2 | — |
| CVE-2026-27903 | high | — | minimatch | 3.1.2 | — |
| CVE-2026-27904 | high | — | minimatch | 3.1.2 | — |
| CVE-2026-32141 | high | — | flatted | 3.2.1 | — |
| CVE-2026-33228 | high | — | flatted | 3.2.1 | — |
| CVE-2026-33671 | high | — | picomatch | 2.2.3 | — |
| CVE-2026-4800 | high | — | lodash | 4.17.21 | — |
| CVE-2023-4316 | medium | — | zod | 3.20.6 | — |
| CVE-2023-44270 | medium | — | postcss | 8.4.14 | — |
| CVE-2024-33883 | medium | — | ejs | 3.1.5 | — |
| CVE-2024-35176 | medium | — | rexml | 3.2 | — |
| CVE-2024-39908 | medium | — | rexml | 3.2 | — |
| CVE-2024-4067 | medium | — | micromatch | 3.1.10 | — |
| CVE-2024-41123 | medium | — | rexml | 3.2 | — |
| CVE-2024-41946 | medium | — | rexml | 3.2 | — |
| CVE-2024-47831 | medium | — | next | 12.3.1 | — |
| CVE-2024-49761 | medium | — | rexml | 3.2 | — |
| CVE-2024-55565 | medium | — | nanoid | 3.3.4 | — |
| CVE-2025-13465 | medium | — | lodash | 4.17.21 | — |
| CVE-2025-27789 | medium | — | @babel/helpers | 7.21.0 | — |
| CVE-2025-27789 | medium | — | @babel/runtime | 7.20.7 | — |
| CVE-2025-55173 | medium | — | next | 12.3.1 | — |
| CVE-2025-57752 | medium | — | next | 12.3.1 | — |
| CVE-2025-57822 | medium | — | next | 12.3.1 | — |
| CVE-2025-59471 | medium | — | next | 12.3.1 | — |
| CVE-2025-6442 | medium | — | webrick | 1.7 | — |
| CVE-2025-64718 | medium | — | js-yaml | 4.1.0 | — |
| CVE-2025-69873 | medium | — | ajv | 6.12.6 | — |
| CVE-2026-27980 | medium | — | next | 12.3.1 | — |
| CVE-2026-29057 | medium | — | next | 12.3.1 | — |
| CVE-2026-2950 | medium | — | lodash | 4.17.21 | — |
| CVE-2026-33532 | medium | — | yaml | 1.10.2 | — |
| CVE-2026-33672 | medium | — | picomatch | 2.2.3 | — |
| CVE-2026-33750 | medium | — | brace-expansion | 1.1.11 | — |
| CVE-2026-41305 | medium | — | postcss | 8.4.14 | — |
| CVE-2021-43307 | low | — | semver-regex | 3.1.3 | — |
| CVE-2023-46298 | low | — | next | 12.3.1 | — |
| CVE-2025-32421 | low | — | next | 12.3.1 | — |
| CVE-2025-54798 | low | — | tmp | 0.0.33 | — |
| CVE-2025-5889 | low | — | brace-expansion | 1.1.11 | — |
| CVE-2026-3449 | low | — | @tootallnate/once | 1.1.2 | — |
Showing 56 of 56