Tools / Heimdall / Security

Security Deep Dive

Heimdall

Security posture and CVE patch evidence from tracked releases.

Back to Tool

8 high-severity dependency CVEs affects v2.8.1.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 4d median Active maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/9 Present

Signed releases Unknown

Latest release artifact signature Latest release

—

SLSA provenance Unknown

Attestation predicate level Latest release

—

SBOM published Unknown

GitHub SBOM API Latest release

—

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 14d ago

Release cadence: weekly Present

4d median over recent releases Release history

Latest release: 17d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 16d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 17d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 17d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 17d ago

3.8/10 Security Score

4.5/10 Scorecard

Dependency Exposure 18 transitive dependency CVEs found in the latest SBOM.

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

9d stale

scorecard

1.80 / 4.0

Score 4.5/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 v2

Vulnerability posture

vulnerability posture

1.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

5.3

10%

supply chain risk: 46.88 transitive cves: 0c/23h

Provenance trust

provenance trust

4.5

40%

scorecard score: 4.5 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 9d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none

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/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

56% Dependency freshness

Scorecard

Scorecard 4.5/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check	Score	Reason
Maintained	10	30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Code-Review	0	Found 1/13 approved changesets -- score normalized to 0
Packaging	-1	packaging workflow not detected
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Fuzzing	0	project is not fuzzed
License	10	license 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
Signed-Releases	-1	no releases found
Security-Policy	4	security policy file detected
Binary-Artifacts	9	binaries present in source code
SAST	0	SAST tool is not run on all commits -- score normalized to 0
Pinned-Dependencies	1	dependency not pinned by hash detected -- score normalized to 1

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1012 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

Still affecting latest (18) All (49)

High 8 Medium 9 Low 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2025-12816	high	—	node-forge	1.3.1	v2.8.0
CVE-2025-66031	high	—	node-forge	1.3.1	v2.8.0
CVE-2026-33671	high	—	picomatch	2.3.1	v2.8.0
CVE-2026-33891	high	—	node-forge	1.3.1	v2.8.0
CVE-2026-33894	high	—	node-forge	1.3.1	v2.8.0
CVE-2026-33895	high	—	node-forge	1.3.1	v2.8.0
CVE-2026-33896	high	—	node-forge	1.3.1	v2.8.0
CVE-2026-4867	high	—	path-to-regexp	0.1.12	v2.8.0
CVE-2025-55166	medium	—	enshrined/svg-sanitize	0.21.0	v2.8.0
CVE-2025-66030	medium	—	node-forge	1.3.1	v2.8.0
CVE-2026-25129	medium	—	psy/psysh	0.12.9	v2.8.0
CVE-2026-30838	medium	—	league/commonmark	2.7.0	v2.8.0
CVE-2026-33347	medium	—	league/commonmark	2.7.0	v2.8.0
CVE-2026-33532	medium	—	yaml	1.10.2	v2.8.0
CVE-2026-33672	medium	—	picomatch	2.3.1	v2.8.0
CVE-2026-33750	medium	—	brace-expansion	1.1.12	v2.8.0
GHSA-r4q5-vmmm-2653	medium	—	follow-redirects	1.15.9	v2.8.0
CVE-2025-7339	low	—	on-headers	1.0.2	v2.8.0

Showing 18 of 49