gitsafehub
github.com/deepakkumar1984/qanet2 ↗

deepakkumar1984/qanet2

scanned 2026-08-09 · git eb1d0ba
2 of 6 checks flagged a security issue
🔴 Needs attention
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 vulnerabilities5Risky code patterns✓Malicious dependencies1Project 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ⓘ 5 found · 1 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious PYSEC-2022-227 Bottle before 0.12.20 mishandles errors during early request binding.
    /workdirs/scan-a6eb07e1-eadc-4fdb-baa4-870824c6edab/requirements.txt
    A package you depend on has a known security hole (CVE-2022-31799). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2021-129 The package bottle from 0 and before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), t
    /workdirs/scan-a6eb07e1-eadc-4fdb-baa4-870824c6edab/requirements.txt
    A package you depend on has a known security hole (CVE-2020-28473). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2017-74 The tqdm._version module in tqdm versions 4.4.1 and 4.10 allows local users to execute arbitrary code via a crafted repo with a malicious git log in the current working directory.
    /workdirs/scan-a6eb07e1-eadc-4fdb-baa4-870824c6edab/requirements.txt
    A package you depend on has a known security hole (CVE-2016-10075). Fix: Update that package to its patched version.
  • Minor PYSEC-2026-1976 tqdm CLI arguments injection attack
    /workdirs/scan-a6eb07e1-eadc-4fdb-baa4-870824c6edab/requirements.txt
    A package you depend on has a known security hole (CVE-2024-34062). Fix: Update that package to its patched version.
  • FYI PYSEC-2014-77 Bottle 0.10.x before 0.10.12, 0.11.x before 0.11.7, and 0.12.x before 0.12.6 does not properly limit content types, which allows remote attackers to bypass intended access restrictions via an accepted
    /workdirs/scan-a6eb07e1-eadc-4fdb-baa4-870824c6edab/requirements.txt
    A package you depend on has a known security hole (CVE-2014-3137). 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ⓘ 1 found

Packages that look intentionally malicious: typosquats, sneaky install scripts.

  • Worth fixing guarddog-pypi-shady-links shady-links match in tqdm 4.70.0
    tqdm
    A dependency shows signs of being intentionally malicious (typosquat, hidden install script, etc.). Fix: Don’t install it until you’ve verified the package. Consider removing it.

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.