kazarmy/maia2

scanned 2026-08-10 · git 67bee6c

2 of 6 checks flagged a security issue

🟡 Worth a look

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 vulnerabilities11Risky 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ⓘ 3 found

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

Worth fixing CVE-2025-2999 A vulnerability was found in PyTorch 2.6.0. It has been rated as criti ...

maia2/requirements.txt

A package you depend on has a known security hole (CVE-2025-2999). 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 ...

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

maia2/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ⓘ 11 found

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing PYSEC-2025-203 An issue in the component torch.linalg.lu of pytorch v2.8.0 allows attackers to cause a Denial of Service (DoS) when performing a slice operation.

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/requirements.txt

A package you depend on has a known security hole (CVE-2025-55551). Fix: Update that package to its patched version.
Worth fixing PYSEC-2025-204 pytorch v2.8.0 was discovered to display unexpected behavior when the components torch.rot90 and torch.randn_like are used together.

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/requirements.txt

A package you depend on has a known security hole (CVE-2025-55552). Fix: Update that package to its patched version.
Worth fixing PYSEC-2025-206 pytorch v2.8.0 was discovered to contain an integer overflow in the component torch.nan_to_num-.long().

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/requirements.txt

A package you depend on has a known security hole (CVE-2025-55554). Fix: Update that package to its patched version.
Worth fixing PYSEC-2026-139 A vulnerability was identified in PyTorch 2.10.0. The affected element is an unknown function of the component pt2 Loading Handler. The manipulation leads to deserialization. The attack can only be pe

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/requirements.txt

A package you depend on has a known security hole (CVE-2026-4538). Fix: Update that package to its patched version.
Worth fixing PYSEC-2026-2286 PyTorch is a Python package that provides tensor computation. Prior to version 2.10.0, a vulnerability in PyTorch's `weights_only` unpickler allows an attacker to craft a malicious checkpoint file (`.

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/requirements.txt

A package you depend on has a known security hole (CVE-2026-24747). Fix: Update that package to its patched version.
Worth fixing GHSA-qfhq-4f3w-5fph PyTorch is vulnerable to memory corruption through its torch.lstm_cell function

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/requirements.txt

A package you depend on has a known security hole (CVE-2025-3001). Fix: Update that package to its patched version.
Worth fixing GHSA-rrmf-rvhw-rf47 PyTorch is vulnerable to memory corruption through its torch.jit.script function

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/requirements.txt

A package you depend on has a known security hole (CVE-2025-3000). Fix: Update that package to its patched version.
Worth fixing GHSA-vgrw-7cvw-pwgx PyTorch is vulnerable to memory corruption through its unpack_sequence function

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/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 PYSEC-2026-1374 filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLock

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/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 PYSEC-2026-1375 filelock has a TOCTOU race condition which allows symlink attacks during lock file creation

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/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 PYSEC-2026-215 Internationalized Domain Names in Applications (IDNA) for Python provides support for Internationalized Domain Names in Applications (IDNA) and Unicode IDNA Compatibility Processing. In versions prior

/workdirs/scan-1d8dcc5a-f0d9-47cd-9e22-196bee312861/maia2/requirements.txt

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