gitsafehub
github.com/julialang/www_old.julialang.org ↗

julialang/www_old.julialang.org

scanned 2026-08-06 · git aa86e1f
2 of 6 checks flagged a security issue
🔴 Needs attention
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets1Vulnerable dependencies68Known OSS vulnerabilities✓Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ 1 found

API keys, passwords or tokens committed into the repo.

  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    _layouts/common.html:21
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 68 found · 6 serious

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

  • Serious CVE-2020-8165 rubygem-activesupport: potentially unintended unmarshalling of user-provided objects in MemCacheStore and RedisCacheStore
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2020-8165). Fix: Update that package to its patched version.
  • Serious CVE-2026-54906 concurrent-ruby: rubygem-concurrent-ruby: concurrent-ruby: Synchronization flaw in ReadWriteLock allows unauthorized lock release and denial of service
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-54906). Fix: Update that package to its patched version.
  • Serious CVE-2020-14001 rubygem-kramdown: processing template options inside documents allows unintended read access or embedded Ruby code execution
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2020-14001). Fix: Update that package to its patched version.
  • Serious CVE-2019-11068 libxslt: xsltCheckRead and xsltCheckWrite routines security bypass by crafted URL
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2019-11068). Fix: Update that package to its patched version.
  • Serious CVE-2019-5477 A command injection vulnerability in Nokogiri v1.10.3 and earlier allo ...
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2019-5477). Fix: Update that package to its patched version.
  • 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-2023-31606 RedCloth: Regular expression denial of service in sanitize_html function
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2023-31606). Fix: Update that package to its patched version.
  • Worth fixing CVE-2012-6684 rubygem-RedCloth: XSS vulnerability
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2012-6684). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-22796 rubygem-activesupport: Regular Expression Denial of Service
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2023-22796). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-33176 Rails: Active Support: Active Support: Denial of Service via large scientific notation strings
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-33176). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-28120 rubygem-activesupport: Possible XSS in SafeBuffer#bytesplice
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2023-28120). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-33169 rails: rails-activesupport: Active Support: Denial of Service via crafted long digit strings
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-33169). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-33170 Rails: Active Support: Active Support: Cross-Site Scripting (XSS) due to improper HTML safety flag propagation in SafeBuffer#%
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-33170). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-32740 rubygem-addressable: ReDoS in templates
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2021-32740). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-35611 addressable: Addressable: Denial of Service via crafted URI templates
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-35611). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54904 concurrent-ruby: rubygem-concurrent-ruby: concurrent-ruby: Denial of Service due to infinite loop in AtomicReference#update
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-54904). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54905 concurrent-ruby: Concurrent-ruby: Incorrect write lock granting leading to broken mutual exclusion
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-54905). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54297 faraday: Faraday: Denial of Service via crafted nested query strings
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-54297). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-25765 Faraday: Faraday: Server-Side Request Forgery via protocol-relative URLs
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2026-25765). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-1000201 ruby-ffi DDL loading issue on Windows OS
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2018-1000201). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-17567 Jekyll through 3.6.2, 3.7.x through 3.7.3, and 3.8.x through 3.8.3 all ...
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2018-17567). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-14404 libxml2: NULL pointer dereference in xmlXPathCompOpEval() function in xpath.c
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2018-14404). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-25032 zlib: A flaw found in zlib when compressing (not decompressing) certain inputs
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2018-25032). Fix: Update that package to its patched version.
  • Worth fixing CVE-2019-13118 libxslt: read of uninitialized stack data due to too narrow xsl:number instruction and an invalid character
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2019-13118). Fix: Update that package to its patched version.
  • Worth fixing CVE-2019-18197 libxslt: use after free in xsltCopyText in transform.c could lead to information disclosure
    Gemfile.lock
    A package you depend on has a known security hole (CVE-2019-18197). Fix: Update that package to its patched version.
… 43 more not shown

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ none found ✓

Your dependencies cross-checked against the OSV vulnerability database.

Nothing found by this check. ✓

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ⓘ didn’t run

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

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OpenSSF Scorecard · 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.