gitsafehub
github.com/uberguidoz/zerorange ↗

uberguidoz/zerorange

scanned 2026-08-05 · git 8556ca9
1 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 dependencies✓Known 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ⓘ none found ✓

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

Nothing found by this check. ✓

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 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-5ab40641-73f1-4075-86e1-11fefa4448ad/requirements_web.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-2024-271 corydolphin/flask-cors is vulnerable to log injection when the log level is set to debug. An attacker can inject fake log entries into the log file by sending a specially crafted GET request containin
    /workdirs/scan-5ab40641-73f1-4075-86e1-11fefa4448ad/requirements_web.txt
    A package you depend on has a known security hole (CVE-2024-1681). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2024-71 A vulnerability in corydolphin/flask-cors up to version 4.0.1 allows the `Access-Control-Allow-Private-Network` CORS header to be set to true by default, without any configuration option. This behavio
    /workdirs/scan-5ab40641-73f1-4075-86e1-11fefa4448ad/requirements_web.txt
    A package you depend on has a known security hole (CVE-2024-6221). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1383 Flask-CORS vulnerable to Improper Handling of Case Sensitivity
    /workdirs/scan-5ab40641-73f1-4075-86e1-11fefa4448ad/requirements_web.txt
    A package you depend on has a known security hole (CVE-2024-6866). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1384 Flask-CORS improper regex path matching vulnerability
    /workdirs/scan-5ab40641-73f1-4075-86e1-11fefa4448ad/requirements_web.txt
    A package you depend on has a known security hole (CVE-2024-6839). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1385 Flask-CORS allows for inconsistent CORS matching
    /workdirs/scan-5ab40641-73f1-4075-86e1-11fefa4448ad/requirements_web.txt
    A package you depend on has a known security hole (CVE-2024-6844). 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-5ab40641-73f1-4075-86e1-11fefa4448ad/requirements_web.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.