Security Deep Dive
geode
Security posture and CVE patch evidence from tracked releases.
9 critical dependency CVEs affects rel/v1.15.4.
Audit transitive dependencies; consider upgrading or pinning replacements.
— Signed
— SLSA
— SBOM
✗ Security policy
Weekly cadence · 3d median
Active maintainer
Trust Signals — 2 of 9 Present
Evidence already collected from releases and repository metadata.
2/9
Present
Signed releases
Unknown
Latest release artifact signature
Latest release
—
SLSA provenance
Unknown
Attestation predicate level
Latest release
—
SBOM published
Unknown
GitHub SBOM API
Latest release
—
SECURITY.md
Absent
GitHub repository metadata
Repository policy
Checked: 16d ago
Release cadence: weekly
Present
3d median over recent releases
Release history
Latest release: 4d ago
Maintainer active
Present
Recent commit activity
Repository
Last commit: 4d ago
Checksums (SHA256SUMS)
Not active yet
SHA256SUMS or equivalent
Release asset
Latest release: 4d ago
GitHub Actions attestation
Not active yet
actions/attest-build-provenance
Workflow file
Latest release: 4d ago
Signing assets
Not active yet
.sig, .crt, cosign.pub, or similar
Release asset
Latest release: 4d ago
4.5/10
Security Score
7.0/10
Scorecard
Dependency Exposure
113 transitive dependency
CVEs found in the latest SBOM.
9 critical.
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
4d stale
scorecard
2.80 / 4.0
Score 7.0/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 100.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
direct cves: clear
cve scan: available
Release responsiveness
release responsiveness
10.0
5%
patch speed days: no_history
Dependency exposure
dependency exposure
0.0
10%
supply chain risk: 100.0
transitive cves: 9c/50h
Provenance trust
provenance trust
7.0
40%
scorecard score: 7.0
openssf badge: none
Maintainer health
maintainer health
10.0
10%
activity freshness: 4d
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 100.0/100
9
Transitive critical CVEs
0
KEV-transitive CVEs
100%
Dependency freshness
Scorecard
Scorecard 7.0/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 22 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| Code-Review | 10 | all changesets reviewed |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Packaging | -1 | packaging workflow not detected |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| License | 10 | license file detected |
| Token-Permissions | 9 | detected GitHub workflow tokens with excessive permissions |
| 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. |
| Security-Policy | 10 | security policy file detected |
| Binary-Artifacts | 9 | binaries present in source code |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Fuzzing | 0 | project is not fuzzed |
| SAST | 10 | SAST tool is run on all commits |
OpenSSF Badge
OpenSSF none
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
101 dependencies scanned
View full dependency list →
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
9
High
50
Medium
46
Low
8
Unknown
0
Critical
9
High
50
Medium
46
Low
8
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2018-20060 | critical | — | urllib3 | — | rel/v2.0.2 |
| CVE-2019-11068 | critical | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2019-5477 | critical | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2020-14001 | critical | — | kramdown | 1.17.0 | rel/v2.0.2 |
| CVE-2022-24790 | critical | — | puma | 5.3.2 | rel/v2.0.2 |
| CVE-2022-25648 | critical | — | git | 1.2.9.1 | rel/v2.0.2 |
| CVE-2022-30123 | critical | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2023-40175 | critical | — | puma | 5.3.2 | rel/v2.0.2 |
| GHSA-353f-x4gh-cqq8 | critical | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2014-10077 | high | — | i18n | 0.7.0 | rel/v2.0.2 |
| CVE-2016-10075 | high | — | tqdm | — | rel/v2.0.2 |
| CVE-2018-18074 | high | — | requests | — | rel/v2.0.2 |
| CVE-2018-25032 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2019-11324 | high | — | urllib3 | — | rel/v2.0.2 |
| CVE-2019-13117 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2019-13118 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2019-18197 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2019-5815 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2020-7212 | high | — | urllib3 | — | rel/v2.0.2 |
| CVE-2020-7595 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2020-8161 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2020-8184 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2021-28834 | high | — | kramdown | 1.17.0 | rel/v2.0.2 |
| CVE-2021-30560 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2021-32740 | high | — | addressable | 2.7.0 | rel/v2.0.2 |
| CVE-2021-33503 | high | — | urllib3 | — | rel/v2.0.2 |
| CVE-2021-3517 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2021-3518 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2021-41098 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2022-23634 | high | — | puma | 5.3.2 | rel/v2.0.2 |
| CVE-2022-24836 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2022-29181 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2022-30122 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2022-44570 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2022-46648 | high | — | git | 1.2.9.1 | rel/v2.0.2 |
| CVE-2022-47318 | high | — | git | 1.2.9.1 | rel/v2.0.2 |
| CVE-2023-27530 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2023-43804 | high | — | urllib3 | — | rel/v2.0.2 |
| CVE-2025-27610 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2025-46727 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2025-59830 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2025-61770 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2025-61771 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2025-61772 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2025-61919 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2025-66418 | high | — | urllib3 | — | rel/v2.0.2 |
| CVE-2025-66471 | high | — | urllib3 | — | rel/v2.0.2 |
| CVE-2026-21441 | high | — | urllib3 | — | rel/v2.0.2 |
| CVE-2026-22860 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-34230 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-34785 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-34829 | high | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-35611 | high | — | addressable | 2.7.0 | rel/v2.0.2 |
| GHSA-c4rq-3m3g-8wgx | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-cgx6-hpwq-fhv5 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-fq42-c5rg-92c2 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-gx8x-g87m-h5q6 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-mrxw-mxhj-p664 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-v6gp-9mmm-c6p5 | high | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2014-1829 | medium | — | requests | — | rel/v2.0.2 |
| CVE-2014-1830 | medium | — | requests | — | rel/v2.0.2 |
| CVE-2015-2296 | medium | — | requests | — | rel/v2.0.2 |
| CVE-2016-9015 | medium | — | urllib3 | — | rel/v2.0.2 |
| CVE-2018-25091 | medium | — | urllib3 | — | rel/v2.0.2 |
| CVE-2019-11236 | medium | — | urllib3 | — | rel/v2.0.2 |
| CVE-2020-26137 | medium | — | urllib3 | — | rel/v2.0.2 |
| CVE-2020-26247 | medium | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2020-26298 | medium | — | redcarpet | 3.2.3 | rel/v2.0.2 |
| CVE-2021-28363 | medium | — | urllib3 | — | rel/v2.0.2 |
| CVE-2021-3537 | medium | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2023-28120 | medium | — | activesupport | 4.2.11.3 | rel/v2.0.2 |
| CVE-2023-32681 | medium | — | requests | — | rel/v2.0.2 |
| CVE-2023-45803 | medium | — | urllib3 | — | rel/v2.0.2 |
| CVE-2024-21647 | medium | — | puma | 5.3.2 | rel/v2.0.2 |
| CVE-2024-25126 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2024-35195 | medium | — | requests | — | rel/v2.0.2 |
| CVE-2024-37891 | medium | — | urllib3 | — | rel/v2.0.2 |
| CVE-2024-45614 | medium | — | puma | 5.3.2 | rel/v2.0.2 |
| CVE-2024-47081 | medium | — | requests | — | rel/v2.0.2 |
| CVE-2025-25184 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2025-27111 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2025-32441 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2025-50181 | medium | — | urllib3 | — | rel/v2.0.2 |
| CVE-2025-50182 | medium | — | urllib3 | — | rel/v2.0.2 |
| CVE-2025-61780 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-25500 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-25645 | medium | — | requests | — | rel/v2.0.2 |
| CVE-2026-25765 | medium | — | faraday | 1.4.2 | rel/v2.0.2 |
| CVE-2026-26961 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-33169 | medium | — | activesupport | 4.2.11.3 | rel/v2.0.2 |
| CVE-2026-33170 | medium | — | activesupport | 4.2.11.3 | rel/v2.0.2 |
| CVE-2026-33176 | medium | — | activesupport | 4.2.11.3 | rel/v2.0.2 |
| CVE-2026-34763 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-34786 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-34826 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-34830 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-34831 | medium | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2026-44312 | medium | — | css_parser | 1.9.0 | rel/v2.0.2 |
| GHSA-2qc6-mcvw-92cw | medium | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-7rrm-v45f-jp64 | medium | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-pxvg-2qj5-37jq | medium | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-v2fc-qm4h-8hqv | medium | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-wx95-c6cv-8532 | medium | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-xc9x-jj77-9p9j | medium | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-xxx9-3xcr-gjj3 | medium | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| CVE-2021-41136 | low | — | puma | 5.3.2 | rel/v2.0.2 |
| CVE-2023-22796 | low | — | activesupport | 4.2.11.3 | rel/v2.0.2 |
| CVE-2024-26141 | low | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2024-26146 | low | — | rack | 1.6.13 | rel/v2.0.2 |
| CVE-2024-34062 | low | — | tqdm | — | rel/v2.0.2 |
| GHSA-5w6v-399v-w3cc | low | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-r95h-9x8f-r3f7 | low | — | nokogiri | 1.10.1 | rel/v2.0.2 |
| GHSA-vvfq-8hwr-qm4m | low | — | nokogiri | 1.10.1 | rel/v2.0.2 |
Showing 113 of 113