Skip to content
Tools / jadx / Security

Security Deep Dive

jadx

Security posture and CVE patch evidence from tracked releases.

Back to Tool

No CVEs tracked against v1.5.5.

— 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: 3mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: 4d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 3mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 3mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 3mo ago
7.4/10 Security Score
4.2/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

3d stale

scorecard

1.68 / 4.0

Score 4.2/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

4.2

40%

scorecard score: 4.2 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 3d

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

Scorecard

Scorecard 4.2/10

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

Check Score Reason
Code-Review 3 Found 9/28 approved changesets -- score normalized to 3
Packaging -1 packaging workflow not detected
Security-Policy 10 security policy file detected
Dangerous-Workflow 10 no dangerous workflow patterns detected
Maintained 10 30 commit(s) and 22 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions 0 detected GitHub workflow tokens with excessive permissions
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies 0 dependency not pinned by hash detected -- score normalized to 0
Binary-Artifacts 9 binaries present in source code
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 0 branch protection not enabled on development/release branches
SAST 0 SAST tool is not run on all commits -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

9 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 are currently attached to the latest SBOM scan. Re-run release ingestion if the latest release does not have SBOM coverage yet.

Beta — feedback welcome: [email protected]