gitsafehub
github.com/entGriff/ezra ↗

entGriff/ezra

scanned 2026-07-25 · git dfcbe27
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 vulnerabilities11Risky 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-2026-48862 mint: Unbounded streams map growth via PUSH_PROMISE without follow-up HEADERS
    mix.lock
    A package you depend on has a known security hole (CVE-2026-48862). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-49754 mint: Unbounded CONTINUATION/HEADERS frame accumulation (CONTINUATION flood)
    mix.lock
    A package you depend on has a known security hole (CVE-2026-49754). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-49753 mint: Content-Length header accepts non-RFC "+" sign prefix
    mix.lock
    A package you depend on has a known security hole (CVE-2026-49753). Fix: Update that package to its patched version.
  • Minor CVE-2026-48861 mint has potential CRLF injection in its HTTP request line via unvalidated `method`/`target`
    mix.lock
    A package you depend on has a known security hole (CVE-2026-48861). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 11 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing EEF-CVE-2026-58226 Unauthenticated denial-of-service via unbounded HPACK integer decoding in hpax
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-58226). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-48862 Unbounded conn.streams growth in Mint HTTP/2 client via unenforced PUSH_PROMISE concurrency
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-48862). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-49753 HTTP response smuggling in Mint HTTP/1 client via lenient Content-Length parsing
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-49753). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-49754 HTTP/2 CONTINUATION flood in Mint client via unbounded header-block accumulation
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-49754). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-56810 mint buffers an entire chunked response chunk in memory in Mint.HTTP1.decode_body/5
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-56810). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-58229 Unbounded HTTP/1 response-header and chunked-trailer accumulation in Mint causes memory-exhaustion DoS
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-58229). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-59246 Zero-length HTTP/2 CONTINUATION frames bypass Mint's header-block byte-size cap and exhaust client memory
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-59246). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-59249 Sign-tolerant HTTP/1 chunk-size parser in Mint enables response smuggling against strict intermediaries on pooled connections
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-59249). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-49755 Decompression bomb DoS in Req via auto-decoded archive and compressed response bodies
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-49755). Fix: Update that package to its patched version.
  • Minor EEF-CVE-2026-48861 CRLF injection in HTTP/1 request line via unvalidated method in Mint
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-48861). Fix: Update that package to its patched version.
  • Minor EEF-CVE-2026-49756 Multipart form-data header injection in Req via unescaped name/filename/content_type
    /workdirs/scan-07306690-3807-4afa-bb38-1a717da1e387/mix.lock
    A package you depend on has a known security hole (CVE-2026-49756). 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.