Tools / SillyTavern / Security

Security Deep Dive

SillyTavern

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects 1.18.0.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA ✓ SBOM ✓ Security policy Monthly cadence · 38d median Active maintainer

Trust Signals — 4 of 9 Present

Evidence already collected from releases and repository metadata.

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

GitHub repository metadata Repository policy

Checked: 22d ago

Release cadence: monthly Present

38d median over recent releases Release history

Latest release: 1mo ago

Maintainer active Present

Recent commit activity Repository

Last commit: 14d 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

4.9/10 Security Score

Dependency Exposure 9 transitive dependency CVEs found in the latest SBOM. 1 critical.

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

14d stale

scorecard

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

1.00 / 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.32 / 10.0

Risk 13.2/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

4.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

8.7

10%

supply chain risk: 13.17 transitive cves: 1c/4h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 14d

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

1 Transitive critical CVEs

0 KEV-transitive CVEs

41% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1182 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 (9) All (9)

Critical 1 High 4 Medium 4

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-41242	critical	—	protobufjs	6.11.4	—
CVE-2026-4800	high	—	lodash-es	4.17.23	—
CVE-2026-6321	high	—	fast-uri	3.1.0	—
CVE-2026-6322	high	—	fast-uri	3.1.0	—
CVE-2026-6951	high	—	simple-git	3.33.0	—
CVE-2024-1899	medium	—	showdown	2.1.0	—
CVE-2026-2950	medium	—	lodash-es	4.17.23	—
CVE-2026-31808	medium	—	file-type	16.5.4	—
CVE-2026-42338	medium	—	ip-address	9.0.5	—

Showing 9 of 9