Security Deep Dive
YARA
Security posture and CVE patch evidence from tracked releases.
No CVEs tracked against v4.5.5.
Trust Signals — 3 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
27d stale
scorecard
1.60 / 4.0
Score 4.0/10
cve health
1.25 / 2.5
⚠ Estimated — no scan yet
patch speed
0.50 / 0.5
⚠ Estimated — no CVE patch history
kev exposure
1.50 / 1.5
No KEV exposure
supply chain risk
-0.02 / 10.0
Risk 0.2/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
5.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
10.0
10%
Provenance trust
provenance trust
4.0
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 0.2/100Scorecard
Scorecard 4.0/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 4 | Found 13/30 approved changesets -- score normalized to 4 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Packaging | -1 | packaging workflow not detected |
| Maintained | 5 | 5 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 5 |
| Security-Policy | 10 | security policy file detected |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 0 | binaries present in source code |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Fuzzing | 10 | project is fuzzed |
| 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. |
| SAST | 0 | SAST tool is not run on all commits -- 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
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.