gitsafehub
github.com/kilimchoi/engineering-blogs ↗

kilimchoi/engineering-blogs

scanned 2026-05-27 · git 50eab27
2 of 6 checks flagged a security issue
🔴 Needs attention
6 checks ran. Start with vulnerable dependencies below.

Informational scan, not a security audit. How this is computed.

Leaked secrets✓Vulnerable dependencies12Known OSS vulnerabilities12Risky code patterns✓Malicious dependencies✓Project health11

Security checks

Leaked secrets — Gitleaksⓘ none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 12 found · 1 serious

Packages you depend on that have known security holes (CVEs).

  • Serious GHSA-353f-x4gh-cqq8 Nokogiri patches vendored libxml2 to resolve multiple CVEs
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-353f-x4gh-cqq8). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-23476 rubygem-nokogiri: Denial of service
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2022-23476). Fix: Update that package to its patched version.
  • Worth fixing GHSA-c4rq-3m3g-8wgx Nokogiri CSS selector tokenizer has regular expression backtracking
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-c4rq-3m3g-8wgx). Fix: Update that package to its patched version.
  • Worth fixing GHSA-mrxw-mxhj-p664 Nokogiri updates packaged libxslt to v1.1.43 to resolve multiple CVEs
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-mrxw-mxhj-p664). Fix: Update that package to its patched version.
  • Worth fixing GHSA-2qc6-mcvw-92cw Update bundled libxml2 to v2.10.3 to resolve multiple CVEs
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-2qc6-mcvw-92cw). Fix: Update that package to its patched version.
  • Worth fixing GHSA-pxvg-2qj5-37jq Update packaged libxml2 to v2.10.4 to resolve multiple CVEs
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-pxvg-2qj5-37jq). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v2fc-qm4h-8hqv Nokogiri XSLT transform has a memory leak
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-v2fc-qm4h-8hqv). Fix: Update that package to its patched version.
  • Worth fixing GHSA-wx95-c6cv-8532 Nokogiri does not check the return value from xmlC14NExecute
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-wx95-c6cv-8532). Fix: Update that package to its patched version.
  • Worth fixing GHSA-xc9x-jj77-9p9j Use-after-free in libxml2 via Nokogiri::XML::Reader
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-xc9x-jj77-9p9j). Fix: Update that package to its patched version.
  • Minor GHSA-5w6v-399v-w3cc Nokogiri updates packaged libxml2 to v2.13.8 to resolve CVE-2025-32414 and CVE-2025-32415
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-5w6v-399v-w3cc). Fix: Update that package to its patched version.
  • Minor GHSA-r95h-9x8f-r3f7 Nokogiri updates packaged libxml2 to v2.12.7 to resolve CVE-2024-34459
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-r95h-9x8f-r3f7). Fix: Update that package to its patched version.
  • Minor GHSA-vvfq-8hwr-qm4m Nokogiri updates packaged libxml2 to 2.13.6 to resolve CVE-2025-24928 and CVE-2024-56171
    Gemfile.lock
    A package you depend on has a known security hole (GHSA-vvfq-8hwr-qm4m). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 12 found · 1 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-353f-x4gh-cqq8 Nokogiri patches vendored libxml2 to resolve multiple CVEs
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-c4rq-3m3g-8wgx Nokogiri CSS selector tokenizer has regular expression backtracking
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-mrxw-mxhj-p664 Nokogiri updates packaged libxslt to v1.1.43 to resolve multiple CVEs
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-qv4q-mr5r-qprj Unchecked return value from xmlTextReaderExpand
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Minor GHSA-5w6v-399v-w3cc Nokogiri updates packaged libxml2 to v2.13.8 to resolve CVE-2025-32414 and CVE-2025-32415
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Minor GHSA-r95h-9x8f-r3f7 Nokogiri updates packaged libxml2 to v2.12.7 to resolve CVE-2024-34459
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Minor GHSA-vvfq-8hwr-qm4m Nokogiri updates packaged libxml2 to 2.13.6 to resolve CVE-2025-24928 and CVE-2024-56171
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GHSA-2qc6-mcvw-92cw Update bundled libxml2 to v2.10.3 to resolve multiple CVEs
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GHSA-pxvg-2qj5-37jq Nokogiri updates packaged libxml2 to v2.10.4 to resolve multiple CVEs
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GHSA-v2fc-qm4h-8hqv Nokogiri XSLT transform has a memory leak
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GHSA-wx95-c6cv-8532 Nokogiri does not check the return value from xmlC14NExecute
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI GHSA-xc9x-jj77-9p9j Nokogiri update packaged libxml2 to v2.12.5 to resolve CVE-2024-25062
    /workdirs/scan-b3fd4acd-2f02-40ac-8c59-6e30a17939da/Gemfile.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.

via OSV-Scanner v1.9.2 · Apache-2.0

Risky code patterns — Semgrepⓘ none found ✓

Code that can be exploited — injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddogⓘ none found ✓

Packages that look intentionally malicious — typosquats, sneaky install scripts.

Nothing found by this check. ✓

via Guarddog v2.10.0 · Apache-2.0

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecardⓘ 11 notes

Maintenance & supply-chain hygiene. A signal about the project — not a vulnerability in your code.

  • Worth fixing scorecard-overall OpenSSF Scorecard overall: 3.6/10
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-CI-Tests CI-Tests scored 0: 0 out of 13 merged PRs checked by a CI test -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-CII-Best-Practices CII-Best-Practices scored 0: no effort to earn an OpenSSF best practices badge detected
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-Fuzzing Fuzzing scored 0: project is not fuzzed
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-License License scored 0: license file not detected
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-Maintained Maintained scored 0: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-Pinned-Dependencies Pinned-Dependencies scored 0: dependency not pinned by hash detected -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-SAST SAST scored 0: SAST tool is not run on all commits -- score normalized to 0
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-Security-Policy Security-Policy scored 0: security policy file not detected
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-Token-Permissions Token-Permissions scored 0: detected GitHub workflow tokens with excessive permissions
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.
  • Minor scorecard-Vulnerabilities Vulnerabilities scored 0: 12 existing vulnerabilities detected
    A project-health signal (maintenance / supply-chain hygiene) — not a vulnerability in your code.

via OpenSSF Scorecard v5.5.0 · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.