gitsafehub
github.com/francescoxx/netflix-backend ↗

francescoxx/netflix-backend

scanned 2026-08-07 · git 7d6d405
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 dependencies8Known OSS vulnerabilities9Risky 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ⓘ 8 found

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

  • Worth fixing CVE-2026-25541 Bytes is a utility library for working with bytes. From version 1.2.1 ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2026-25541). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-31812 quinn-proto: quinn-proto: Denial of Service via crafted QUIC Initial packet
    Cargo.lock
    A package you depend on has a known security hole (CVE-2026-31812). Fix: Update that package to its patched version.
  • Worth fixing GHSA-4w2j-m93h-cj5j Quinn: Remote memory exhaustion in quinn-proto from unbounded out-of-order stream reassembly
    Cargo.lock
    A package you depend on has a known security hole (GHSA-4w2j-m93h-cj5j). Fix: Update that package to its patched version.
  • Worth fixing GHSA-82j2-j2ch-gfr8 rustls-webpki: Denial of service via panic on malformed CRL BIT STRING
    Cargo.lock
    A package you depend on has a known security hole (GHSA-82j2-j2ch-gfr8). Fix: Update that package to its patched version.
  • Worth fixing GHSA-pwjx-qhcg-rvj4 webpki: CRLs not considered authoritative by Distribution Point due to faulty matching logic
    Cargo.lock
    A package you depend on has a known security hole (GHSA-pwjx-qhcg-rvj4). Fix: Update that package to its patched version.
  • Minor GHSA-cq8v-f236-94qc Rand is unsound with a custom logger using rand::rng()
    Cargo.lock
    A package you depend on has a known security hole (GHSA-cq8v-f236-94qc). Fix: Update that package to its patched version.
  • Minor GHSA-965h-392x-2mh5 webpki: Name constraints for URI names were incorrectly accepted
    Cargo.lock
    A package you depend on has a known security hole (GHSA-965h-392x-2mh5). Fix: Update that package to its patched version.
  • Minor GHSA-xgp8-3hg3-c2mh webpki: Name constraints were accepted for certificates asserting a wildcard name
    Cargo.lock
    A package you depend on has a known security hole (GHSA-xgp8-3hg3-c2mh). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 9 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing RUSTSEC-2026-0007 Integer overflow in `BytesMut::reserve`
    /workdirs/scan-353493f3-b0eb-46a8-a787-cc02a79c2748/Cargo.lock
    A package you depend on has a known security hole (CVE-2026-25541). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2026-0037 Denial of service in Quinn endpoints
    /workdirs/scan-353493f3-b0eb-46a8-a787-cc02a79c2748/Cargo.lock
    A package you depend on has a known security hole (CVE-2026-31812). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2026-0185 Remote memory exhaustion in quinn-proto from unbounded out-of-order stream reassembly
    /workdirs/scan-353493f3-b0eb-46a8-a787-cc02a79c2748/Cargo.lock
    A package you depend on has a known security hole (CVE-2026-25800). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2026-0049 CRLs not considered authoritative by Distribution Point due to faulty matching logic
    /workdirs/scan-353493f3-b0eb-46a8-a787-cc02a79c2748/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2026-0104 Reachable panic in certificate revocation list parsing
    /workdirs/scan-353493f3-b0eb-46a8-a787-cc02a79c2748/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Minor RUSTSEC-2026-0098 Name constraints for URI names were incorrectly accepted
    /workdirs/scan-353493f3-b0eb-46a8-a787-cc02a79c2748/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Minor RUSTSEC-2026-0099 Name constraints were accepted for certificates asserting a wildcard name
    /workdirs/scan-353493f3-b0eb-46a8-a787-cc02a79c2748/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2021-0141 dotenv is Unmaintained
    /workdirs/scan-353493f3-b0eb-46a8-a787-cc02a79c2748/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0097 Rand is unsound with a custom logger using `rand::rng()`
    /workdirs/scan-353493f3-b0eb-46a8-a787-cc02a79c2748/Cargo.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ⓘ 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.