Tools / leantime / Security

Security Deep Dive

leantime

Security posture and CVE patch evidence from tracked releases.

Back to Tool

12 high-severity dependency CVEs affects v3.8.0.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 6d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/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 Present

GitHub repository metadata Repository policy

Checked: 18d ago

Release cadence: weekly Present

6d median over recent releases Release history

Latest release: 7d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 7d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 7d ago

Signing assets Not active yet

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

Latest release: 7d ago

4.0/10 Security Score

5.1/10 Scorecard

Dependency Exposure 24 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

1d stale

scorecard

2.04 / 4.0

Score 5.1/10

cve health

0.25 / 2.5

⚠ No direct scan — 0c/18h 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 36.8/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

6.3

10%

supply chain risk: 36.82 transitive cves: 0c/18h

Provenance trust

provenance trust

5.1

40%

scorecard score: 5.1 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

59% Dependency freshness

Scorecard

Scorecard 5.1/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 12 issue activity found in the last 90 days -- score normalized to 10
Security-Policy	10	security policy file detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
Code-Review	5	Found 5/9 approved changesets -- score normalized to 5
Packaging	-1	packaging workflow not 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
Binary-Artifacts	10	no binaries found in the repo
License	10	license file detected
Branch-Protection	6	branch protection is not maximal on development and all release branches
Signed-Releases	0	Project has not signed or included provenance with any releases.
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0
Fuzzing	0	project is not fuzzed
SAST	0	SAST tool is not run on all commits -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1529 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 (24) All (44)

High 12 Medium 11 Low 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-32141	high	—	flatted	3.3.3	v3.8.0
CVE-2026-32313	high	—	robrichards/xmlseclibs	3.1.3	v3.8.0
CVE-2026-32935	high	—	phpseclib/phpseclib	3.0.46	v3.8.0
CVE-2026-33228	high	—	flatted	3.3.3	v3.8.0
CVE-2026-33671	high	—	picomatch	2.3.1	v3.8.0
CVE-2026-33891	high	—	node-forge	1.3.2	v3.8.0
CVE-2026-33894	high	—	node-forge	1.3.2	v3.8.0
CVE-2026-33895	high	—	node-forge	1.3.2	v3.8.0
CVE-2026-33896	high	—	node-forge	1.3.2	v3.8.0
CVE-2026-44167	high	—	phpseclib/phpseclib	3.0.46	v3.8.0
CVE-2026-4867	high	—	path-to-regexp	0.1.12	v3.8.0
CVE-2026-6321	high	—	fast-uri	3.0.6	v3.8.0
CVE-2025-66578	medium	—	robrichards/xmlseclibs	3.1.3	v3.8.0
CVE-2026-25129	medium	—	psy/psysh	0.12.9	v3.8.0
CVE-2026-30838	medium	—	league/commonmark	2.7.0	v3.8.0
CVE-2026-33347	medium	—	league/commonmark	2.7.0	v3.8.0
CVE-2026-33532	medium	—	yaml	1.10.2	v3.8.0
CVE-2026-33672	medium	—	picomatch	2.3.1	v3.8.0
CVE-2026-41238	medium	—	dompurify	3.3.3	v3.8.0
CVE-2026-41239	medium	—	dompurify	3.3.3	v3.8.0
CVE-2026-41240	medium	—	dompurify	3.3.3	v3.8.0
GHSA-39q2-94rc-95cp	medium	—	dompurify	3.3.3	v3.8.0
GHSA-r4q5-vmmm-2653	medium	—	follow-redirects	1.15.9	v3.8.0
CVE-2026-40194	low	—	phpseclib/phpseclib	3.0.46	v3.8.0

Showing 24 of 44