gitsafehub
github.com/leandrocp/safe_code ↗

leandrocp/safe_code

scanned 2026-08-12 · git f182999
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 secrets✓Vulnerable dependencies2Known OSS vulnerabilities7Risky code patterns✓Malicious dependencies✓Project 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ⓘ 2 found

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

  • Worth fixing CVE-2026-32689 Phoenix: Long-poll NDJSON body splitting causes large memory allocation
    mix.lock
    A package you depend on has a known security hole (CVE-2026-32689). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-8468 Plug: Unbounded buffer accumulation in multipart header parsing causes denial of service
    mix.lock
    A package you depend on has a known security hole (CVE-2026-8468). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 7 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing EEF-CVE-2026-32689 Long-poll NDJSON body splitting causes unbounded memory allocation in Phoenix
    /workdirs/scan-8f0c4486-c11f-4040-9ff0-b6557cbfdc75/mix.lock
    A package you depend on has a known security hole (CVE-2026-32689). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-56811 Phoenix transports do not limit channel joins per connection, enabling process-exhaustion denial of service
    /workdirs/scan-8f0c4486-c11f-4040-9ff0-b6557cbfdc75/mix.lock
    A package you depend on has a known security hole (CVE-2026-56811). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-56812 Phoenix JavaScript presence client crashes on presence keys colliding with Object.prototype members in Presence.syncState/syncDiff
    /workdirs/scan-8f0c4486-c11f-4040-9ff0-b6557cbfdc75/mix.lock
    A package you depend on has a known security hole (CVE-2026-56812). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-56814 Plug: multipart :length limit is not charged for part headers, enabling unbounded temp-file creation (denial of service)
    /workdirs/scan-8f0c4486-c11f-4040-9ff0-b6557cbfdc75/mix.lock
    A package you depend on has a known security hole (CVE-2026-56814). Fix: Update that package to its patched version.
  • Worth fixing EEF-CVE-2026-8468 Unbounded buffer accumulation in multipart header parsing causes denial of service in plug
    /workdirs/scan-8f0c4486-c11f-4040-9ff0-b6557cbfdc75/mix.lock
    A package you depend on has a known security hole (CVE-2026-8468). Fix: Update that package to its patched version.
  • Minor EEF-CVE-2026-64941 Open redirect in Phoenix.LiveView.validate_local_url!/2 via ASCII tab, LF and CR
    /workdirs/scan-8f0c4486-c11f-4040-9ff0-b6557cbfdc75/mix.lock
    A package you depend on has a known security hole (CVE-2026-64941). Fix: Update that package to its patched version.
  • Minor EEF-CVE-2026-56813 Cookie attribute injection in Plug.Conn.Cookies.encode/2
    /workdirs/scan-8f0c4486-c11f-4040-9ff0-b6557cbfdc75/mix.lock
    A package you depend on has a known security hole (CVE-2026-56813). 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.