gitsafehub
github.com/jwangkun/gbc-madai ↗

jwangkun/gbc-madai

scanned 2026-08-11 · git 681126e
2 of 6 checks flagged a security issue
🔴 Needs attention
Only 3 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets5Vulnerable dependencies96Known OSS vulnerabilities—Risky code patterns✓Malicious dependencies—Project health—

Security checks

Leaked secrets — Gitleaksⓘ 5 found

API keys, passwords or tokens committed into the repo.

  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    llm_backend/app/graphrag/tests/integration/storage/test_blob_pipeline_storage.py:11
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    llm_backend/app/graphrag/tests/integration/storage/test_factory.py:20
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    llm_backend/app/graphrag/tests/integration/storage/test_factory.py:22
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    llm_backend/app/graphrag/tests/integration/storage/test_cosmosdb_storage.py:15
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    llm_backend/app/graphrag/tests/smoke/test_fixtures.py:29
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 96 found · 2 serious

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

  • Serious CVE-2025-43859 h11: h11 accepts some malformed Chunked-Encoding bodies
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2025-43859). Fix: Update that package to its patched version.
  • Serious CVE-2025-14009 nltk: Zip Slip Vulnerability in nltk Leading to Code Execution
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2025-14009). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-69223 aiohttp: AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2025-69223). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-69244 AIOHTTP is an asynchronous HTTP client/server framework for asyncio an ...
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-69244). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-69227 aiohttp: aiohttp: Denial of Service via specially crafted POST request
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2025-69227). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-69228 aiohttp: aiohttp: Denial of Service via memory exhaustion from crafted POST request
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2025-69228). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-69229 aiohttp: AIOHTTP: Denial of Service via excessive CPU usage in chunked message handling
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2025-69229). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-22815 aiohttp: AIOHTTP: Denial of Service via insufficient header/trailer handling
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-22815). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-34515 aiohttp: AIOHTTP: Information disclosure via static resource handler on Windows
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-34515). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-34516 aiohttp: AIOHTTP: Denial of Service via excessive multipart headers
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-34516). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-34525 aiohttp: aiohttp: Security bypass via multiple Host headers
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-34525). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-34993 aiohttp: AIOHTTP: Arbitrary code execution via untrusted input to CookieJar.load()
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-34993). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-47265 python-aiohttp: AIOHTTP: Information disclosure via improper handling of cookies during cross-origin redirects
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-47265). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54273 aiohttp: AIOHTTP: Denial of Service via excessive pipelined requests
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-54273). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54274 aiohttp: aiohttp: Denial of Service via incomplete websocket frame payloads
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-54274). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54276 aiohttp: aiohttp: Information disclosure via DigestAuthMiddleware after cross-origin redirect
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-54276). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54277 aiohttp: aiohttp: Denial of Service via oversized HTTP request lines bypassing max_line_size check
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-54277). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54278 aiohttp: aiohttp: Denial of Service due to excessive memory consumption from compressed request body
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-54278). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-59881 AIOHTTP is an asynchronous HTTP client/server framework for asyncio an ...
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-59881). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-69243 AIOHTTP is an asynchronous HTTP client/server framework for asyncio an ...
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-69243). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-21226 Azure Core is vulnerable to deserialization of untrusted data
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-21226). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-26007 cryptography: cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-26007). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-69247 cryptography is a package designed to expose cryptographic primitives ...
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-69247). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-69249 python-cryptography is a package designed to expose cryptographic prim ...
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (CVE-2026-69249). Fix: Update that package to its patched version.
  • Worth fixing GHSA-537c-gmf6-5ccf Vulnerable OpenSSL included in cryptography wheels
    llm_backend/app/graphrag/poetry.lock
    A package you depend on has a known security hole (GHSA-537c-gmf6-5ccf). Fix: Update that package to its patched version.
… 71 more not shown

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ timed out

Your dependencies cross-checked against the OSV vulnerability database.

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

via OSV-Scanner v1.9.2 · Apache-2.0

error: timeout after 400s

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ⓘ timed out

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: pypi:timeout

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.