gitsafehub
github.com/lizhuofan-curry/wenqu ↗

lizhuofan-curry/wenqu

scanned 2026-08-07 · git 8474e3c
1 of 6 checks flagged a security issue
🟡 Worth a look
Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secretsVulnerable dependenciesKnown 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 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 11 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing PYSEC-2026-215 Internationalized Domain Names in Applications (IDNA) for Python provides support for Internationalized Domain Names in Applications (IDNA) and Unicode IDNA Compatibility Processing. In versions prior
    /workdirs/scan-924d9cf3-062f-46cd-95ec-f953185bb135/api/requirements.txt
    A package you depend on has a known security hole (CVE-2026-45409). 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-924d9cf3-062f-46cd-95ec-f953185bb135/api/requirements.txt
    A package you depend on has a known security hole (CVE-2016-10075). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-215 Internationalized Domain Names in Applications (IDNA) for Python provides support for Internationalized Domain Names in Applications (IDNA) and Unicode IDNA Compatibility Processing. In versions prior
    /workdirs/scan-924d9cf3-062f-46cd-95ec-f953185bb135/services/api/requirements-dev.txt
    A package you depend on has a known security hole (CVE-2026-45409). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2023-117 A ReDoS issue was discovered in pygments/lexers/smithy.py in pygments through 2.15.0 via SmithyLexer.
    /workdirs/scan-924d9cf3-062f-46cd-95ec-f953185bb135/services/api/requirements-dev.txt
    A package you depend on has a known security hole (CVE-2022-40896). 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-924d9cf3-062f-46cd-95ec-f953185bb135/services/api/requirements-dev.txt
    A package you depend on has a known security hole (CVE-2016-10075). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-215 Internationalized Domain Names in Applications (IDNA) for Python provides support for Internationalized Domain Names in Applications (IDNA) and Unicode IDNA Compatibility Processing. In versions prior
    /workdirs/scan-924d9cf3-062f-46cd-95ec-f953185bb135/services/api/requirements.txt
    A package you depend on has a known security hole (CVE-2026-45409). 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-924d9cf3-062f-46cd-95ec-f953185bb135/services/api/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-924d9cf3-062f-46cd-95ec-f953185bb135/api/requirements.txt
    A package you depend on has a known security hole (CVE-2024-34062). Fix: Update that package to its patched version.
  • Minor PYSEC-2026-2987 Pygments has Regular Expression Denial of Service (ReDoS) due to Inefficient Regex for GUID Matching
    /workdirs/scan-924d9cf3-062f-46cd-95ec-f953185bb135/services/api/requirements-dev.txt
    A package you depend on has a known security hole (CVE-2026-4539). Fix: Update that package to its patched version.
  • Minor PYSEC-2026-1976 tqdm CLI arguments injection attack
    /workdirs/scan-924d9cf3-062f-46cd-95ec-f953185bb135/services/api/requirements-dev.txt
    A package you depend on has a known security hole (CVE-2024-34062). Fix: Update that package to its patched version.
  • Minor PYSEC-2026-1976 tqdm CLI arguments injection attack
    /workdirs/scan-924d9cf3-062f-46cd-95ec-f953185bb135/services/api/requirements.txt
    A package you depend on has a known security hole (CVE-2024-34062). 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 couldn’t run

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

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via Guarddog v2.10.0 · Apache-2.0

error: npm:ERROR: Error while scanning. Received HTTPSConnectionPool(host='registry.npmjs.org', port=443): Max retries exceeded wit

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.