Security Deep Dive
Gradle
Security posture and CVE patch evidence from tracked releases.
3 high-severity dependency CVEs affects v9.5.1.
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
1d stale
scorecard
2.12 / 4.0
Score 5.3/10
cve health
0.25 / 2.5
⚠ No direct scan — 0c/4h 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
-0.80 / 10.0
Risk 8.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
1.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
9.2
10%
Provenance trust
provenance trust
5.3
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 8.0/100Scorecard
Scorecard 5.3/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 7 | Found 11/15 approved changesets -- score normalized to 7 |
| Maintained | 10 | 30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10 |
| CII-Best-Practices | 5 | badge detected: Passing |
| Packaging | -1 | packaging workflow not detected |
| License | 10 | license file detected |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Signed-Releases | -1 | no releases found |
| Branch-Protection | 3 | branch protection is not maximal on development and all release branches |
| Security-Policy | 10 | security policy file detected |
| SAST | 9 | SAST tool detected but not run on all commits |
| Fuzzing | 0 | project is not fuzzed |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Binary-Artifacts | 0 | binaries present in source code |
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
0
High
3
Medium
8
Low
0
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2025-67030 | high | — | org.codehaus.plexus:plexus-utils | 4.0.2 | v8.14.5 |
| CVE-2026-3505 | high | — | org.bouncycastle:bcpg-jdk18on | 1.80 | v8.14.5 |
| CVE-2026-5598 | high | — | org.bouncycastle:bcprov-jdk18on | 1.80 | v8.14.5 |
| CVE-2025-48924 | medium | — | commons-lang:commons-lang | 2.6 | v8.14.5 |
| CVE-2026-0636 | medium | — | org.bouncycastle:bcprov-jdk18on | 1.80 | v8.14.5 |
| CVE-2026-3260 | medium | — | io.undertow:undertow-core | 2.3.24.Final | v8.14.5 |
| CVE-2026-34477 | medium | — | org.apache.logging.log4j:log4j-core | 2.25.3 | v8.14.5 |
| CVE-2026-34478 | medium | — | org.apache.logging.log4j:log4j-core | 2.25.3 | v8.14.5 |
| CVE-2026-34480 | medium | — | org.apache.logging.log4j:log4j-core | 2.25.3 | v8.14.5 |
| CVE-2026-5588 | medium | — | org.bouncycastle:bcpkix-jdk18on | 1.80 | v8.14.5 |
| GHSA-72hv-8253-57qq | medium | — | com.fasterxml.jackson.core:jackson-core | 2.20.2 | v8.14.5 |
Showing 11 of 15