Security Deep Dive
Heimdall
Security posture and CVE patch evidence from tracked releases.
23 high-severity dependency CVEs affects v2.7.6.
Review the dependency vulnerabilities below.
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
0.48 / 1.0
204d stale
scorecard
1.48 / 4.0
Score 3.7/10
cve health
0.25 / 2.5
⚠ No direct scan — 0c/23h 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 46.9/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
1.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
5.3
10%
Provenance trust
provenance trust
3.7
40%
Maintainer health
maintainer health
4.8
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 46.9/100Scorecard
Scorecard 3.7/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 3 | Found 4/13 approved changesets -- score normalized to 3 |
| Maintained | 1 | 0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1 |
| Packaging | -1 | packaging workflow not detected |
| 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 |
| Fuzzing | 0 | project is not fuzzed |
| License | 10 | license file detected |
| Signed-Releases | -1 | no releases found |
| 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 |
| Binary-Artifacts | 9 | binaries present in source code |
| Security-Policy | 4 | security policy file detected |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| 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
0
High
23
Medium
21
Low
5
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2025-12816 | high | — | node-forge | 1.3.1 | — |
| CVE-2025-64500 | high | — | symfony/http-foundation | 7.3.1 | — |
| CVE-2025-66031 | high | — | node-forge | 1.3.1 | — |
| CVE-2026-24765 | high | — | phpunit/phpunit | 10.5.47 | — |
| 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-29063 | high | — | immutable | 5.1.3 | — |
| CVE-2026-29074 | high | — | svgo | 2.8.0 | — |
| CVE-2026-32141 | high | — | flatted | 3.3.3 | — |
| 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-44728 | high | — | @babel/plugin-transform-modules-systemjs | 7.27.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.0.6 | — |
| CVE-2026-6322 | high | — | fast-uri | 3.0.6 | — |
| GHSA-27qh-8cxx-2cr5 | high | — | aws/aws-sdk-php | 3.349.3 | — |
| GHSA-5c6j-r48x-rmvq | high | — | serialize-javascript | 6.0.2 | — |
| CVE-2025-13465 | medium | — | lodash | 4.17.21 | — |
| CVE-2025-14761 | medium | — | aws/aws-sdk-php | 3.349.3 | — |
| CVE-2025-15284 | medium | — | qs | 6.13.0 | — |
| CVE-2025-30359 | medium | — | webpack-dev-server | 4.15.2 | — |
| CVE-2025-30360 | medium | — | webpack-dev-server | 4.15.2 | — |
| CVE-2025-55166 | medium | — | enshrined/svg-sanitize | 0.21.0 | — |
| CVE-2025-64718 | medium | — | js-yaml | 4.1.0 | — |
| CVE-2025-66030 | medium | — | node-forge | 1.3.1 | — |
| CVE-2025-69873 | medium | — | ajv | 6.12.6 | — |
| CVE-2026-24739 | medium | — | symfony/process | 7.3.0 | — |
| CVE-2026-25129 | medium | — | psy/psysh | 0.12.9 | — |
| CVE-2026-2739 | medium | — | bn.js | 5.2.2 | — |
| CVE-2026-2950 | medium | — | lodash | 4.17.21 | — |
| CVE-2026-30838 | medium | — | league/commonmark | 2.7.0 | — |
| CVE-2026-33347 | medium | — | league/commonmark | 2.7.0 | — |
| CVE-2026-33532 | medium | — | yaml | 1.10.2 | — |
| 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-41305 | medium | — | postcss | 8.5.6 | — |
| GHSA-r4q5-vmmm-2653 | medium | — | follow-redirects | 1.15.9 | — |
| CVE-2025-14505 | low | — | elliptic | 6.6.1 | — |
| CVE-2025-68157 | low | — | webpack | 5.100.1 | — |
| CVE-2025-68458 | low | — | webpack | 5.100.1 | — |
| CVE-2025-7339 | low | — | on-headers | 1.0.2 | — |
| CVE-2026-2391 | low | — | qs | 6.13.0 | — |
Showing 49 of 49