Skip to content
Tools / Radarr / Security

Security Deep Dive

Radarr

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 critical dependency CVEs affects v6.1.1.10360.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA ✓ SBOM ✓ Security policy Unknown cadence 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 Present
GitHub SBOM API Latest release
Last verified: 28d ago
SECURITY.md Present
GitHub repository metadata Repository policy
Checked: 18d ago
Release cadence Unknown
12-release median Release history
Latest release: 2mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: 4d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 2mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 2mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 2mo ago
4.1/10 Security Score
5.8/10 Scorecard
Dependency Exposure 37 transitive dependency CVEs found in the latest SBOM. 2 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

4d stale

scorecard

2.32 / 4.0

Score 5.8/10

cve health

0.00 / 2.5

⚠ No direct scan — 2c/18h 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 45.0/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

5.5

10%

supply chain risk: 45.02 transitive cves: 2c/18h

Provenance trust

provenance trust

5.8

40%

scorecard score: 5.8 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 4d

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 45.0/100
2 Transitive critical CVEs
0 KEV-transitive CVEs
49% Dependency freshness

Scorecard

Scorecard 5.8/10

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

Check Score Reason
Maintained 10 22 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Code-Review 3 Found 10/26 approved changesets -- score normalized to 3
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Packaging -1 packaging workflow not detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
Token-Permissions 9 detected GitHub workflow tokens with excessive permissions
Security-Policy 10 security policy file detected
License 10 license file detected
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
Signed-Releases 0 Project has not signed or included provenance with any releases.
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0
Binary-Artifacts 9 binaries present in source code
SAST 2 SAST tool is not run on all commits -- score normalized to 2
Fuzzing 0 project is not fuzzed

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1096 dependencies scanned View full dependency list →

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

Critical

2

High

18

Medium

13

Low

4

Unknown

0

Critical 2 High 18 Medium 13 Low 4
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2017-9785 critical Nancy 1.4.3
CVE-2026-27212 critical swiper 8.3.2
CVE-2020-1045 high Microsoft.Owin 2.1.0
CVE-2021-27293 high RestSharp 105.2.3
CVE-2022-29117 high Microsoft.Owin 2.1.0
CVE-2024-21538 high cross-spawn 7.0.3
CVE-2024-21907 high Newtonsoft.Json 6.0.6
CVE-2025-64756 high glob 11.0.0
CVE-2026-26996 high minimatch 3.1.2
CVE-2026-27903 high minimatch 3.1.2
CVE-2026-27904 high minimatch 3.1.2
CVE-2026-29063 high immutable 4.3.7
CVE-2026-32141 high flatted 3.3.1
CVE-2026-33228 high flatted 3.3.1
CVE-2026-33671 high picomatch 2.3.1
CVE-2026-44728 high @babel/plugin-transform-modules-systemjs 7.27.1
CVE-2026-4800 high lodash 4.17.21
CVE-2026-6321 high fast-uri 3.0.2
CVE-2026-6322 high fast-uri 3.0.2
GHSA-5c6j-r48x-rmvq high serialize-javascript 6.0.2
CVE-2021-23382 medium postcss 6.0.23
CVE-2021-29060 medium color-string 0.3.0
CVE-2023-44270 medium postcss 6.0.23
CVE-2025-13465 medium lodash 4.17.21
CVE-2025-15284 medium qs 6.13.0
CVE-2025-64718 medium js-yaml 4.1.0
CVE-2025-69873 medium ajv 8.17.1
CVE-2026-2950 medium lodash 4.17.21
CVE-2026-33532 medium yaml 1.10.2
CVE-2026-33672 medium picomatch 2.3.1
CVE-2026-33750 medium brace-expansion 2.0.1
CVE-2026-34043 medium serialize-javascript 6.0.2
CVE-2026-41305 medium postcss 8.5.6
CVE-2025-5889 low brace-expansion 2.0.1
CVE-2025-68157 low webpack 5.95.0
CVE-2025-68458 low webpack 5.95.0
CVE-2026-2391 low qs 6.13.0

Showing 37 of 37

Beta — feedback welcome: [email protected]