timeatronics/zetla

scanned 2026-08-03 · git 459430f

2 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 dependencies3Known OSS vulnerabilities4Risky code patterns✓Malicious dependencies✓Project 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 120s

Vulnerable dependencies — Trivyⓘ 3 found

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

Worth fixing CVE-2026-4372 HuggingFace transformers vulnerable to remote code execution

uv.lock

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

uv.lock

A package you depend on has a known security hole (CVE-2026-5241). Fix: Update that package to its patched version.
Worth fixing CVE-2026-1839 transformers: HuggingFace Transformers: Arbitrary code execution via malicious checkpoint file

uv.lock

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

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 4 found · 1 serious

Your dependencies cross-checked against the OSV vulnerability database.

Serious PYSEC-2026-2290 A vulnerability in the LightGlue model loading path of huggingface/transformers version 5.2.0 allows an attacker-controlled model repository to execute arbitrary code during model initialization. The

/workdirs/scan-fa78f58a-0cde-4dcf-9d75-cac5128108b5/uv.lock

A package you depend on has a known security hole (CVE-2026-5241). Fix: Update that package to its patched version.
Worth fixing PYSEC-2025-217 Hugging Face Transformers X-CLIP Checkpoint Conversion Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on af

/workdirs/scan-fa78f58a-0cde-4dcf-9d75-cac5128108b5/uv.lock

A package you depend on has a known security hole (CVE-2025-14929). Fix: Update that package to its patched version.
Worth fixing PYSEC-2026-2288 A vulnerability in the HuggingFace Transformers library, specifically in the `Trainer` class, allows for arbitrary code execution. The `_load_rng_state()` method in `src/transformers/trainer.py` at li

/workdirs/scan-fa78f58a-0cde-4dcf-9d75-cac5128108b5/uv.lock

A package you depend on has a known security hole (CVE-2026-1839). Fix: Update that package to its patched version.
Worth fixing PYSEC-2026-2289 A critical remote code execution vulnerability exists in all versions of the HuggingFace transformers library prior to version 5.3.0. The vulnerability allows an attacker to craft a malicious `config.

/workdirs/scan-fa78f58a-0cde-4dcf-9d75-cac5128108b5/uv.lock

A package you depend on has a known security hole (CVE-2026-4372). 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ⓘ none found ✓

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

Nothing found by this check. ✓

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.