Security Deep Dive
DeTT&CT
Security posture and CVE patch evidence from tracked releases.
No CVEs tracked against v2.2.0.
Trust Signals — 1 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
0.98 / 1.0
36d stale
scorecard
1.48 / 4.0
Score 3.7/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 v2Vulnerability posture
vulnerability posture
10.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
10.0
10%
Provenance trust
provenance trust
3.7
40%
Maintainer health
maintainer health
9.8
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.
Scorecard
Scorecard 3.7/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 0 | Found 1/30 approved changesets -- score normalized to 0 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Maintained | 1 | 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1 |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Security-Policy | 0 | security policy file not detected |
| Fuzzing | 0 | project is not fuzzed |
| License | 10 | license file detected |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Signed-Releases | -1 | no releases found |
| 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 |
| Packaging | 10 | packaging workflow detected |
OpenSSF Badge
Badge indicates adherence to open-source best practices.