Tools / stash / Security

Security Deep Dive

stash

Security posture and CVE patch evidence from tracked releases.

Back to Tool

10 high-severity dependency CVEs affects v0.31.1.

Review the dependency vulnerabilities below.

— Signed — SLSA ✓ SBOM ✗ Security policy Unknown cadence 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 Present

GitHub SBOM API Latest release

Last verified: 28d ago

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 17d ago

Release cadence Unknown

12-release median Release history

Latest release: 1mo ago

Maintainer active Present

Recent commit activity Repository

Last commit: 6d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 1mo ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 1mo ago

Signing assets Not active yet

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

Latest release: 1mo ago

3.5/10 Security Score

4.4/10 Scorecard

Pending CVE Patch Speed

Open CVEs Open CVEs detected for latest version.

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

6d stale

scorecard

1.76 / 4.0

Score 4.4/10

cve health

0.00 / 2.5

Open CVEs detected

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

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: open cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

7.9

10%

supply chain risk: 20.8 transitive cves: 0c/10h

Provenance trust

provenance trust

4.4

40%

scorecard score: 4.4 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 6d

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

60% Dependency freshness

Scorecard

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

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1467 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 (25) All (25)

High 10 Medium 8 Low 2 Unknown 5

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2020-8203	high	—	lodash.pick	4.4.0	—
CVE-2024-4068	high	—	braces	1.8.5	—
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.4	—
CVE-2026-33671	high	—	picomatch	2.3.1	—
CVE-2026-4800	high	—	lodash	4.17.21	—
CVE-2026-6321	high	—	fast-uri	3.1.0	—
CVE-2026-6322	high	—	fast-uri	3.1.0	—
CVE-2024-4067	medium	—	micromatch	2.3.11	—
CVE-2025-13465	medium	—	lodash	4.17.21	—
CVE-2025-64718	medium	—	js-yaml	3.14.1	—
CVE-2026-2950	medium	—	lodash	4.17.21	—
CVE-2026-33532	medium	—	yaml	2.8.1	—
CVE-2026-33672	medium	—	picomatch	2.3.1	—
CVE-2026-33750	medium	—	brace-expansion	1.1.12	—
CVE-2026-41305	medium	—	postcss	8.5.8	—
CVE-2023-36308	low	—	github.com/disintegration/imaging	v1.6.2	—
CVE-2026-24001	low	—	diff	4.0.2	—
CVE-2025-69725	unknown	—	github.com/go-chi/chi/v5	v5.2.2	—
CVE-2026-27141	unknown	—	golang.org/x/net	v0.50.0	—
CVE-2026-33812	unknown	—	golang.org/x/image	v0.38.0	—
CVE-2026-33813	unknown	—	golang.org/x/image	v0.38.0	—
CVE-2026-33814	unknown	—	golang.org/x/net	v0.50.0	—

Showing 25 of 25