Security Deep Dive
lemmy
Security posture and CVE patch evidence from tracked releases.
1 high-severity dependency CVE affects 0.19.20.
Review the dependency vulnerabilities below.
Trust Signals — 2 of 9 Present
Evidence already collected from releases and repository metadata.
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
7d stale
scorecard
2.08 / 4.0
Score 5.2/10
cve health
0.00 / 2.5
⚠ No direct scan — 3c/16h 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 44.9/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
5.5
10%
Provenance trust
provenance trust
5.2
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
8.5
10%
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 44.9/100Scorecard
Scorecard 5.2/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Packaging | -1 | packaging workflow not detected |
| Maintained | 10 | 30 commit(s) and 25 issue activity found in the last 90 days -- score normalized to 10 |
| Dangerous-Workflow | -1 | no workflows found |
| Token-Permissions | -1 | No tokens found |
| Code-Review | 9 | Found 29/30 approved changesets -- score normalized to 9 |
| Security-Policy | 9 | security policy file detected |
| 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 |
| Fuzzing | 0 | project is not fuzzed |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Branch-Protection | -1 | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| 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
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
0
High
1
Medium
4
Low
2
Unknown
2
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-4867 | high | — | path-to-regexp | 0.1.12 | 0.19.19 |
| CVE-2023-49092 | medium | — | rsa | 0.9.10 | 0.19.19 |
| CVE-2024-12224 | medium | — | idna | 0.3.0 | 0.19.19 |
| CVE-2026-42180 | medium | — | lemmy_api_common | 0.19.16 | 0.19.19 |
| CVE-2026-42181 | medium | — | lemmy_api_common | 0.19.16 | 0.19.19 |
| GHSA-cq8v-f236-94qc | low | — | rand | 0.10.0 | 0.19.19 |
| GHSA-ff9q-rm55-q7qr | low | — | diesel-async | 0.8.0 | 0.19.19 |
| RUSTSEC-2024-0320 | unknown | — | yaml-rust | 0.4.5 | 0.19.19 |
| RUSTSEC-2026-0097 | unknown | — | rand | 0.10.0 | 0.19.19 |
Showing 9 of 60