gitsafehub
github.com/nvlabs/pixeldit ↗

nvlabs/pixeldit

scanned 2026-08-13 · git 41f7300
1 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 secretsVulnerable dependencies10Known OSS vulnerabilitiesRisky 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 10 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-2026-44513 Diffusers: Diffusers: Arbitrary remote code execution via `trust_remote_code` bypass
    requirements.txt
    A package you depend on has a known security hole (CVE-2026-44513). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-45804 diffusers: Diffusers: Arbitrary code execution due to trust_remote_code guard bypass
    requirements.txt
    A package you depend on has a known security hole (CVE-2026-45804). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-2999 A vulnerability was found in PyTorch 2.6.0. It has been rated as criti ...
    requirements.txt
    A package you depend on has a known security hole (CVE-2025-2999). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-3730 A vulnerability, which was classified as problematic, was found in PyT ...
    requirements.txt
    A package you depend on has a known security hole (CVE-2025-3730). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-4372 HuggingFace transformers vulnerable to remote code execution
    requirements.txt
    A package you depend on has a known security hole (CVE-2026-4372). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-5241 python-transformers: python-transformers: Arbitrary code execution due to overridden trust_remote_code setting
    requirements.txt
    A package you depend on has a known security hole (CVE-2026-5241). Fix: Update that package to its patched version.
  • Minor CVE-2025-2953 torch: PyTorch torch.mkldnn_max_pool2d denial of service
    requirements.txt
    A package you depend on has a known security hole (CVE-2025-2953). Fix: Update that package to its patched version.
  • Minor CVE-2025-3000 A vulnerability classified as critical has been found in PyTorch 2.6.0 ...
    requirements.txt
    A package you depend on has a known security hole (CVE-2025-3000). Fix: Update that package to its patched version.
  • Minor CVE-2025-3001 A vulnerability classified as critical was found in PyTorch 2.6.0. Thi ...
    requirements.txt
    A package you depend on has a known security hole (CVE-2025-3001). 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 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.