gitsafehub
github.com/ehazlett/site_templates ↗

ehazlett/site_templates

scanned 2026-08-12 · git c90fc5f
2 of 6 checks flagged a security issue
🟡 Worth a look
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secretsVulnerable dependencies4Known OSS vulnerabilities8Risky code patternsMalicious dependenciesProject health

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 4 found

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

  • Worth fixing CVE-2018-1000656 python-flask: Denial of Service via crafted JSON file
    flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2018-1000656). Fix: Update that package to its patched version.
  • Worth fixing CVE-2019-1010083 python-flask: unexpected memory usage can lead to denial of service via crafted encoded JSON data
    flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2019-1010083). Fix: Update that package to its patched version.
  • Worth fixing CVE-2023-30861 flask: Possible disclosure of permanent session cookie due to missing Vary: Cookie header
    flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2023-30861). Fix: Update that package to its patched version.
  • Minor CVE-2026-27205 flask: Flask: Information disclosure via improper caching of session data
    flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2026-27205). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 8 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing PYSEC-2018-66 The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of servic
    /workdirs/scan-d900c3b2-9c1c-4236-b69a-4a3bf3976723/flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2018-1000656). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2019-179 The Pallets Project Flask before 1.0 is affected by: unexpected memory usage. The impact is: denial of service. The attack vector is: crafted encoded JSON data. The fixed version is: 1. NOTE: this may
    /workdirs/scan-d900c3b2-9c1c-4236-b69a-4a3bf3976723/flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2019-1010083). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2023-62 Flask is a lightweight WSGI web application framework. When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by the proxy
    /workdirs/scan-d900c3b2-9c1c-4236-b69a-4a3bf3976723/flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2023-30861). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2151 Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Us
    /workdirs/scan-d900c3b2-9c1c-4236-b69a-4a3bf3976723/flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2026-27205). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2018-66 The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of servic
    /workdirs/scan-d900c3b2-9c1c-4236-b69a-4a3bf3976723/flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2018-1000656). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2019-179 The Pallets Project Flask before 1.0 is affected by: unexpected memory usage. The impact is: denial of service. The attack vector is: crafted encoded JSON data. The fixed version is: 1. NOTE: this may
    /workdirs/scan-d900c3b2-9c1c-4236-b69a-4a3bf3976723/flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2019-1010083). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2023-62 Flask is a lightweight WSGI web application framework. When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by the proxy
    /workdirs/scan-d900c3b2-9c1c-4236-b69a-4a3bf3976723/flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2023-30861). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2151 Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Us
    /workdirs/scan-d900c3b2-9c1c-4236-b69a-4a3bf3976723/flask_redis/requirements.txt
    A package you depend on has a known security hole (CVE-2026-27205). 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 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.