Security Deep Dive
apko
Security posture and CVE patch evidence from tracked releases.
No known vulnerabilities in v1.2.15.
5 CVEs patched in tracked history. Median patch time: 0 days.
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
Up to date
scorecard
3.52 / 4.0
Score 8.8/10
cve health
2.50 / 2.5
No open CVEs
patch speed
0.50 / 0.5
0d avg
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
8.8
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.
Scorecard
Scorecard 8.8/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 10 | all changesets reviewed |
| Maintained | 10 | 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Token-Permissions | 10 | GitHub workflow tokens follow principle of least privilege |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Pinned-Dependencies | 10 | all dependencies are pinned |
| Fuzzing | 0 | project is not fuzzed |
| License | 10 | license file detected |
| Security-Policy | 10 | security policy file detected |
| Branch-Protection | 8 | branch protection is not maximal on development and all release branches |
| Signed-Releases | 8 | 5 out of the last 5 releases have a total of 5 signed artifacts. |
| Packaging | 10 | packaging workflow detected |
| SAST | 10 | SAST tool is run on all commits |
OpenSSF Badge
Badge indicates adherence to open-source best practices.
CVE Patch History
Median patch time: 0 daysTracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.
CVEs Patched by Year
| CVE | Severity | EPSS | Disclosed | Fixed in | Days to fix | vs Ecosystem Median | KEV |
|---|---|---|---|---|---|---|---|
| GO-2026-4410 | unknown | — | — | v1.1.1 | — | — | — |
| GHSA-5g94-c2wx-8pxw | High | — | — | v1.1.0 | — | — | — |
| GHSA-6p9p-q6wh-9j89 | unknown | — | — | v1.1.0 | — | — | — |
| GO-2026-4405 | unknown | — | — | v1.1.0 | — | — | — |
| GO-2026-4406 | unknown | — | — | v1.1.0 | — | — | — |
KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.