Tools / sandbox / Security

Security Deep Dive

sandbox

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 high-severity dependency CVEs affects v1.9.3.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 2d 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: 23d ago

Release cadence: weekly Present

2d median over recent releases Release history

Latest release: 5d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 5d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 5d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 5d ago

Signing assets Not active yet

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

Latest release: 5d ago

4.2/10 Security Score

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

5d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

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

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

2.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

5.3

10%

supply chain risk: 47.2 transitive cves: 2c/19h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 5d

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

40% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

958 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 (8) All (50)

High 2 Medium 5 Low 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-30922	high	—	pyasn1	0.6.2	v1.9.3
CVE-2026-34070	high	—	langchain-core	1.2.19	v1.9.3
CVE-2026-25528	medium	—	langsmith	0.4.37	v1.9.3
CVE-2026-28684	medium	—	python-dotenv	1.1.1	v1.9.3
CVE-2026-40087	medium	—	langchain-core	1.2.19	v1.9.3
CVE-2026-41182	medium	—	langsmith	0.4.37	v1.9.3
GHSA-67mh-4wv8-2f99	medium	—	esbuild	0.21.5	v1.9.3
CVE-2026-41488	low	—	langchain-openai	1.0.1	v1.9.3

Showing 8 of 50