Security Deep Dive
kill-the-newsletter
Security posture and CVE patch evidence from tracked releases.
3 critical dependency CVEs affects v2.0.9.
Audit transitive dependencies; consider upgrading or pinning replacements.
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
0.76 / 1.0
111d stale
scorecard
1.00 / 4.0
Score 2.5/10
cve health
0.00 / 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
-1.50 / 10.0
Risk 95.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
0.5
10%
Provenance trust
provenance trust
2.5
40%
Maintainer health
maintainer health
7.6
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 95.0/100Scorecard
Scorecard 2.5/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Binary-Artifacts | 10 | no binaries found in the repo |
| Packaging | -1 | packaging workflow not detected |
| Maintained | 0 | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Code-Review | 0 | Found 0/30 approved changesets -- score normalized to 0 |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| SAST | 0 | no SAST tool detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0 | security policy file not detected |
| License | 10 | license file detected |
| Fuzzing | 0 | project is not fuzzed |
| Branch-Protection | 0 | branch protection not enabled on development/release branches |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
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
3
High
41
Medium
30
Low
11
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2019-5477 | critical | — | nokogiri | 1.10.3 | — |
| CVE-2022-30123 | critical | — | rack | 2.0.7 | — |
| GHSA-353f-x4gh-cqq8 | critical | — | nokogiri | 1.10.3 | — |
| CVE-2018-25032 | high | — | nokogiri | 1.10.3 | — |
| CVE-2019-13117 | high | — | nokogiri | 1.10.3 | — |
| CVE-2019-13118 | high | — | nokogiri | 1.10.3 | — |
| CVE-2019-18197 | high | — | nokogiri | 1.10.3 | — |
| CVE-2019-5815 | high | — | nokogiri | 1.10.3 | — |
| CVE-2020-7595 | high | — | nokogiri | 1.10.3 | — |
| CVE-2020-8161 | high | — | rack | 2.0.7 | — |
| CVE-2020-8184 | high | — | rack | 2.0.7 | — |
| CVE-2021-30560 | high | — | nokogiri | 1.10.3 | — |
| CVE-2021-3517 | high | — | nokogiri | 1.10.3 | — |
| CVE-2021-3518 | high | — | nokogiri | 1.10.3 | — |
| CVE-2021-41098 | high | — | nokogiri | 1.10.3 | — |
| CVE-2022-24836 | high | — | nokogiri | 1.10.3 | — |
| CVE-2022-29181 | high | — | nokogiri | 1.10.3 | — |
| CVE-2022-29970 | high | — | sinatra | 2.0.5 | — |
| CVE-2022-30122 | high | — | rack | 2.0.7 | — |
| CVE-2022-44570 | high | — | rack | 2.0.7 | — |
| CVE-2022-45442 | high | — | sinatra | 2.0.5 | — |
| CVE-2023-27530 | high | — | rack | 2.0.7 | — |
| CVE-2025-27610 | high | — | rack | 2.0.7 | — |
| CVE-2025-46727 | high | — | rack | 2.0.7 | — |
| CVE-2025-59830 | high | — | rack | 2.0.7 | — |
| CVE-2025-61770 | high | — | rack | 2.0.7 | — |
| CVE-2025-61771 | high | — | rack | 2.0.7 | — |
| CVE-2025-61772 | high | — | rack | 2.0.7 | — |
| CVE-2025-61919 | high | — | rack | 2.0.7 | — |
| CVE-2026-22860 | high | — | rack | 2.0.7 | — |
| CVE-2026-26996 | high | — | minimatch | 9.0.5 | — |
| CVE-2026-27903 | high | — | minimatch | 9.0.5 | — |
| CVE-2026-27904 | high | — | minimatch | 9.0.5 | — |
| CVE-2026-33671 | high | — | picomatch | 2.3.1 | — |
| CVE-2026-34230 | high | — | rack | 2.0.7 | — |
| CVE-2026-34785 | high | — | rack | 2.0.7 | — |
| CVE-2026-34829 | high | — | rack | 2.0.7 | — |
| CVE-2026-4800 | high | — | lodash | 4.17.21 | — |
| GHSA-c4rq-3m3g-8wgx | high | — | nokogiri | 1.10.3 | — |
| GHSA-cgx6-hpwq-fhv5 | high | — | nokogiri | 1.10.3 | — |
| GHSA-fq42-c5rg-92c2 | high | — | nokogiri | 1.10.3 | — |
| GHSA-gx8x-g87m-h5q6 | high | — | nokogiri | 1.10.3 | — |
| GHSA-mrxw-mxhj-p664 | high | — | nokogiri | 1.10.3 | — |
| GHSA-v6gp-9mmm-c6p5 | high | — | nokogiri | 1.10.3 | — |
| CVE-2019-16782 | medium | — | rack | 2.0.7 | — |
| CVE-2020-26247 | medium | — | nokogiri | 1.10.3 | — |
| CVE-2020-8130 | medium | — | rake | 12.3.2 | — |
| CVE-2021-3537 | medium | — | nokogiri | 1.10.3 | — |
| CVE-2024-21510 | medium | — | sinatra | 2.0.5 | — |
| CVE-2024-25126 | medium | — | rack | 2.0.7 | — |
| CVE-2025-13465 | medium | — | lodash | 4.17.21 | — |
| CVE-2025-25184 | medium | — | rack | 2.0.7 | — |
| CVE-2025-27111 | medium | — | rack | 2.0.7 | — |
| CVE-2025-32441 | medium | — | rack | 2.0.7 | — |
| CVE-2025-61780 | medium | — | rack | 2.0.7 | — |
| CVE-2026-25500 | medium | — | rack | 2.0.7 | — |
| CVE-2026-26961 | medium | — | rack | 2.0.7 | — |
| CVE-2026-2950 | medium | — | lodash | 4.17.21 | — |
| CVE-2026-33672 | medium | — | picomatch | 2.3.1 | — |
| CVE-2026-33750 | medium | — | brace-expansion | 1.1.11 | — |
| CVE-2026-34763 | medium | — | rack | 2.0.7 | — |
| CVE-2026-34786 | medium | — | rack | 2.0.7 | — |
| CVE-2026-34826 | medium | — | rack | 2.0.7 | — |
| CVE-2026-34830 | medium | — | rack | 2.0.7 | — |
| CVE-2026-34831 | medium | — | rack | 2.0.7 | — |
| CVE-2026-41305 | medium | — | postcss | 8.5.6 | — |
| GHSA-2qc6-mcvw-92cw | medium | — | nokogiri | 1.10.3 | — |
| GHSA-7rrm-v45f-jp64 | medium | — | nokogiri | 1.10.3 | — |
| GHSA-pxvg-2qj5-37jq | medium | — | nokogiri | 1.10.3 | — |
| GHSA-v2fc-qm4h-8hqv | medium | — | nokogiri | 1.10.3 | — |
| GHSA-vvjj-xcjg-gr5g | medium | — | nodemailer | 8.0.1 | — |
| GHSA-wx95-c6cv-8532 | medium | — | nokogiri | 1.10.3 | — |
| GHSA-xc9x-jj77-9p9j | medium | — | nokogiri | 1.10.3 | — |
| GHSA-xxx9-3xcr-gjj3 | medium | — | nokogiri | 1.10.3 | — |
| CVE-2022-44571 | low | — | rack | 2.0.7 | — |
| CVE-2022-44572 | low | — | rack | 2.0.7 | — |
| CVE-2023-27539 | low | — | rack | 2.0.7 | — |
| CVE-2024-26141 | low | — | rack | 2.0.7 | — |
| CVE-2024-26146 | low | — | rack | 2.0.7 | — |
| CVE-2025-5889 | low | — | brace-expansion | 1.1.11 | — |
| CVE-2025-61921 | low | — | sinatra | 2.0.5 | — |
| GHSA-5w6v-399v-w3cc | low | — | nokogiri | 1.10.3 | — |
| GHSA-c7w3-x93f-qmm8 | low | — | nodemailer | 8.0.1 | — |
| GHSA-r95h-9x8f-r3f7 | low | — | nokogiri | 1.10.3 | — |
| GHSA-vvfq-8hwr-qm4m | low | — | nokogiri | 1.10.3 | — |
Showing 85 of 85