Skip to content
Tools / weblate / Security

Security Deep Dive

weblate

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against weblate-2026.6.1.

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

3.36 / 4.0

Score 8.4/10

cve health

0.00 / 2.5

⚠ No direct scan — 1c/11h 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 26.4/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

7.4

10%

supply chain risk: 26.35 transitive cves: 1c/11h

Provenance trust

provenance trust

8.4

40%

scorecard score: 8.4 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 26.4/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
82% Dependency freshness

Scorecard

Scorecard 8.4/10

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

Check Score Reason
Code-Review 0 Found 0/6 approved changesets -- score normalized to 0
Maintained 10 30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Security-Policy 10 security policy file detected
Dependency-Update-Tool 10 update tool detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
Packaging -1 packaging workflow not detected
Binary-Artifacts 10 no binaries found in the repo
Token-Permissions 10 GitHub workflow tokens follow principle of least privilege
CII-Best-Practices 5 badge detected: Passing
License 10 license file detected
Vulnerabilities 10 0 existing vulnerabilities detected
Signed-Releases 8 5 out of the last 5 releases have a total of 5 signed artifacts.
Fuzzing 10 project is fuzzed
Pinned-Dependencies 10 all dependencies are pinned
SAST 9 SAST tool is not run on all commits -- score normalized to 9
Branch-Protection 3 branch protection is not maximal on development and all release branches
CI-Tests 10 8 out of 8 merged PRs checked by a CI test -- score normalized to 10
Contributors 10 project has 23 contributing companies or organizations

Dependency Vulnerabilities

621 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

0

High

0

Medium

0

Low

0

Unknown

0

No dependency CVEs match this filter.

Showing 0 of 37

Beta — feedback welcome: [email protected]