xiaohuailabs/supervision

scanned 2026-08-13 · git 9ded70c

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 secrets—Vulnerable dependencies21Known OSS vulnerabilities—Risky code patterns✓Malicious dependencies5Project health—

Security checks

Leaked secrets — Gitleaksⓘ timed out

API keys, passwords or tokens committed into the repo.

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

via Gitleaks v8.21.2 · MIT

error: timeout after 400s

Vulnerable dependencies — Trivyⓘ 21 found · 1 serious

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

Serious CVE-2023-50447 pillow: Arbitrary Code Execution via the environment parameter

poetry.lock

A package you depend on has a known security hole (CVE-2023-50447). Fix: Update that package to its patched version.
Worth fixing CVE-2023-45139 fonttools: XML External Entity Injection (XXE) Vulnerability

poetry.lock

A package you depend on has a known security hole (CVE-2023-45139). Fix: Update that package to its patched version.
Worth fixing CVE-2025-66034 fonttools: fontTools: Arbitrary file write leading to remote code execution via malicious .designspace file

poetry.lock

A package you depend on has a known security hole (CVE-2025-66034). Fix: Update that package to its patched version.
Worth fixing GHSA-qr4w-53vh-m672 opencv-python bundled libwebp binaries in wheels that are vulnerable to CVE-2023-4863

poetry.lock

A package you depend on has a known security hole (GHSA-qr4w-53vh-m672). Fix: Update that package to its patched version.
Worth fixing GHSA-jh2j-j4j9-crg3 opencv-python-headless bundled libwebp binaries in wheels that are vulnerable to CVE-2023-4863

poetry.lock

A package you depend on has a known security hole (GHSA-jh2j-j4j9-crg3). Fix: Update that package to its patched version.
Worth fixing CVE-2024-28219 python-pillow: buffer overflow in _imagingcms.c

poetry.lock

A package you depend on has a known security hole (CVE-2024-28219). Fix: Update that package to its patched version.
Worth fixing CVE-2026-54058 Pillow: Pillow: Memory disclosure or denial of service via crafted McIdas AREA image

poetry.lock

A package you depend on has a known security hole (CVE-2026-54058). Fix: Update that package to its patched version.
Worth fixing CVE-2026-54059 python-pillow: Pillow: Denial of Service via crafted PCF font data

poetry.lock

A package you depend on has a known security hole (CVE-2026-54059). Fix: Update that package to its patched version.
Worth fixing CVE-2026-54060 python-pillow: Pillow: Denial of Service via excessive memory allocation when processing font files

poetry.lock

A package you depend on has a known security hole (CVE-2026-54060). Fix: Update that package to its patched version.
Worth fixing CVE-2026-55379 python-pillow: Pillow: Denial of Service via crafted BDF font file

poetry.lock

A package you depend on has a known security hole (CVE-2026-55379). Fix: Update that package to its patched version.
Worth fixing CVE-2026-55380 python-pillow: Pillow: Denial of Service via crafted GD 2.x image file

poetry.lock

A package you depend on has a known security hole (CVE-2026-55380). Fix: Update that package to its patched version.
Worth fixing CVE-2026-59197 Pillow: Pillow: Native heap out-of-bounds write

poetry.lock

A package you depend on has a known security hole (CVE-2026-59197). Fix: Update that package to its patched version.
Worth fixing CVE-2026-59199 Pillow: Pillow: Denial of Service via out-of-bounds write in image processing

poetry.lock

A package you depend on has a known security hole (CVE-2026-59199). Fix: Update that package to its patched version.
Worth fixing CVE-2026-59200 Pillow: Pillow: Denial of service via crafted PDF stream

poetry.lock

A package you depend on has a known security hole (CVE-2026-59200). Fix: Update that package to its patched version.
Worth fixing CVE-2026-59204 Pillow: Pillow: Denial of Service via crafted JPEG2000 image

poetry.lock

A package you depend on has a known security hole (CVE-2026-59204). Fix: Update that package to its patched version.
Worth fixing CVE-2026-59205 Pillow: Pillow: Controlled native heap corruption in ImageCms.ImageCmsTransform.apply API

poetry.lock

A package you depend on has a known security hole (CVE-2026-59205). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42308 Pillow: python: Pillow: Denial of Service via integer overflow in font processing

poetry.lock

A package you depend on has a known security hole (CVE-2026-42308). Fix: Update that package to its patched version.
Worth fixing CVE-2026-42310 Pillow: Pillow: Denial of Service via malicious PDF processing

poetry.lock

A package you depend on has a known security hole (CVE-2026-42310). Fix: Update that package to its patched version.
Worth fixing CVE-2026-55798 python-pillow: Pillow: Arbitrary command injection via shell metacharacters in file paths

poetry.lock

A package you depend on has a known security hole (CVE-2026-55798). Fix: Update that package to its patched version.
Worth fixing CVE-2026-59198 Pillow: Pillow: Information disclosure via TGA RLE encoder out-of-bounds read

poetry.lock

A package you depend on has a known security hole (CVE-2026-59198). Fix: Update that package to its patched version.
Worth fixing CVE-2024-5569 github.com/jaraco/zipp: Denial of Service (infinite loop) via crafted zip file in jaraco/zipp

poetry.lock

A package you depend on has a known security hole (CVE-2024-5569). Fix: Update that package to its patched version.

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ⓘ 5 found · 3 serious

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

Serious guarddog-pypi-code-execution code-execution match in ultralytics 8.4.118

ultralytics

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.
Serious guarddog-pypi-code-execution code-execution match in numpy 1.24.4

numpy

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.
Serious guarddog-pypi-code-execution code-execution match in matplotlib 3.7.2

matplotlib

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.
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.
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.