gitsafehub
github.com/hacksider/short-video-creator ↗

hacksider/short-video-creator

scanned 2026-08-07 · git 6547110
1 of 6 checks flagged a security issue
🔴 Needs attention
Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets✓Vulnerable dependencies56Known OSS vulnerabilities✓Risky 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ⓘ 56 found · 1 serious

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

  • Serious CVE-2025-32434 PyTorch is a Python package that provides tensor computation with stro ...
    requirements.txt
    A package you depend on has a known security hole (CVE-2025-32434). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-56201 jinja2: Jinja has a sandbox breakout through malicious filenames
    requirements.txt
    A package you depend on has a known security hole (CVE-2024-56201). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-56326 jinja2: Jinja has a sandbox breakout through indirect reference to format method
    requirements.txt
    A package you depend on has a known security hole (CVE-2024-56326). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-27516 jinja2: Jinja sandbox breakout through attr filter selecting format method
    requirements.txt
    A package you depend on has a known security hole (CVE-2025-27516). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-68146 filelock: filelock: Time-of-Check-Time-of-Use (TOCTOU) race condition and symlink attack allows arbitrary file corruption or truncation
    requirements.txt
    A package you depend on has a known security hole (CVE-2025-68146). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-22701 filelock: filelock Time-of-Check-Time-of-Use (TOCTOU) in SoftFileLock
    requirements.txt
    A package you depend on has a known security hole (CVE-2026-22701). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-45409 python-idna: idna: Denial of Service via specially crafted long inputs
    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 CVE-2026-25990 pillow: Pillow: Out-of-bounds Write via Specially Crafted PSD Image
    requirements.txt
    A package you depend on has a known security hole (CVE-2026-25990). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-40192 Pillow: Pillow: Denial of Service via decompression bomb in FITS image processing
    requirements.txt
    A package you depend on has a known security hole (CVE-2026-40192). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-42311 Pillow: python-pillow: Pillow: Arbitrary code execution via malicious PSD file processing
    requirements.txt
    A package you depend on has a known security hole (CVE-2026-42311). 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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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
    requirements.txt
    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-47081 requests: Requests vulnerable to .netrc credentials leak via malicious URLs
    requirements.txt
    A package you depend on has a known security hole (CVE-2024-47081). Fix: Update that package to its patched version.
… 31 more not shown

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ none found ✓

Your dependencies cross-checked against the OSV vulnerability database.

Nothing found by this check. ✓

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: pypi:ERROR: Error while scanning. Received 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte Traceback (

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.