Skip to content
Tools / Unsloth / Security

Security Deep Dive

Unsloth

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against v0.1.50-beta.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 6d 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
6d median over recent releases Release history
Latest release: 6d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 8d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 6d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 6d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 6d ago
8.3/10 Security Score
6.3/10 Scorecard

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.52 / 4.0

Score 6.3/10

cve health

2.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

0.00 / 10.0

Risk 0.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

10.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

10.0

10%

supply chain risk: 0.0 transitive cves: 0c/0h

Provenance trust

provenance trust

6.3

40%

scorecard score: 6.3 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.

Scorecard

Scorecard 6.3/10

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

Check Score Reason
Dependency-Update-Tool 10 update tool detected
Code-Review 6 Found 19/30 approved changesets -- score normalized to 6
Maintained 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow 10 no dangerous workflow patterns detected
Packaging -1 packaging workflow not detected
Binary-Artifacts 8 binaries present in source code
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Token-Permissions 9 detected GitHub workflow tokens with excessive permissions
Security-Policy 0 security policy file not detected
Fuzzing 0 project is not fuzzed
Pinned-Dependencies 3 dependency not pinned by hash detected -- score normalized to 3
Vulnerabilities 0 59 existing vulnerabilities detected
Signed-Releases -1 internal error: error during graphqlHandler.setup: internal error: githubv4.Query: GET https://api.github.com/repos/unslothai/unsloth/releases: 503 No server is currently available to service your request. Sorry about that. Please try resubmitting your request and contact us if the problem persists. []
License 10 license file detected
SAST 4 SAST tool is not run on all commits -- score normalized to 4
Branch-Protection -1 internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
CI-Tests 10 29 out of 29 merged PRs checked by a CI test -- score normalized to 10
Contributors 10 project has 14 contributing companies or organizations

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Beta — feedback welcome: [email protected]