Security Deep Dive
Capistrano
Security posture and CVE patch evidence from tracked releases.
2 critical dependency CVEs affects v3.20.1.
Audit transitive dependencies; consider upgrading or pinning replacements.
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
1.00 / 1.0
17d stale
scorecard
1.60 / 4.0
Score 4.0/10
cve health
0.00 / 2.5
⚠ No direct scan — 2c/19h transitive 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 46.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
5.4
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 46.0/100Scorecard
Scorecard 4.0/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 2 | 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Code-Review | 6 | Found 16/24 approved changesets -- score normalized to 6 |
| Packaging | -1 | packaging workflow not 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 |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Security-Policy | 0 | security policy file not detected |
| Fuzzing | 0 | project is not fuzzed |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| 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 | -1 | no releases found |
| 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
2
High
19
Medium
19
Low
4
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2020-14001 | critical | — | kramdown | 1.17.0 | v3.20.1 |
| GHSA-353f-x4gh-cqq8 | critical | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2014-10077 | high | — | i18n | 0 | v3.20.1 |
| CVE-2018-25032 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2021-28834 | high | — | kramdown | 1.17.0 | v3.20.1 |
| CVE-2021-30560 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2021-32740 | high | — | addressable | 2.5.2 | v3.20.1 |
| CVE-2021-3517 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2021-3518 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2021-41098 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2022-24836 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2022-29181 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2022-31163 | high | — | tzinfo | 1.2.5 | v3.20.1 |
| CVE-2024-22051 | high | — | commonmarker | 0.17.13 | v3.20.1 |
| CVE-2026-35611 | high | — | addressable | 2.5.2 | v3.20.1 |
| GHSA-c4rq-3m3g-8wgx | high | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-cgx6-hpwq-fhv5 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-fq42-c5rg-92c2 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-gx8x-g87m-h5q6 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-mrxw-mxhj-p664 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-v6gp-9mmm-c6p5 | high | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2013-4492 | medium | — | i18n | 0 | v3.20.1 |
| CVE-2020-26247 | medium | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2020-8130 | medium | — | rake | 10.0.0 | v3.20.1 |
| CVE-2021-3537 | medium | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2023-28120 | medium | — | activesupport | 4.2.10 | v3.20.1 |
| CVE-2026-33169 | medium | — | activesupport | 4.2.10 | v3.20.1 |
| CVE-2026-33170 | medium | — | activesupport | 4.2.10 | v3.20.1 |
| CVE-2026-33176 | medium | — | activesupport | 4.2.10 | v3.20.1 |
| GHSA-2qc6-mcvw-92cw | medium | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-48wp-p9qv-4j64 | medium | — | commonmarker | 0.17.13 | v3.20.1 |
| GHSA-4qw4-jpp4-8gvp | medium | — | commonmarker | 0.17.13 | v3.20.1 |
| GHSA-636f-xm5j-pj9m | medium | — | commonmarker | 0.17.13 | v3.20.1 |
| GHSA-7rrm-v45f-jp64 | medium | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-7vh7-fw88-wj87 | medium | — | commonmarker | 0.17.13 | v3.20.1 |
| GHSA-pxvg-2qj5-37jq | medium | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-v2fc-qm4h-8hqv | medium | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-wx95-c6cv-8532 | medium | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-xc9x-jj77-9p9j | medium | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-xxx9-3xcr-gjj3 | medium | — | nokogiri | 1.10.8 | v3.20.1 |
| CVE-2023-22796 | low | — | activesupport | 4.2.10 | v3.20.1 |
| GHSA-5w6v-399v-w3cc | low | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-r95h-9x8f-r3f7 | low | — | nokogiri | 1.10.8 | v3.20.1 |
| GHSA-vvfq-8hwr-qm4m | low | — | nokogiri | 1.10.8 | v3.20.1 |
Showing 44 of 44