gitsafehub
github.com/appliedscientific/cardiosafe-benchmark ↗

appliedscientific/cardiosafe-benchmark

scanned 2026-08-01 · git a481ffb
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 dependencies5Known OSS vulnerabilities94Risky 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 400s

Vulnerable dependencies — Trivyⓘ 5 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 ...
    space/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 ...
    space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-3730). Fix: Update that package to its patched version.
  • Minor CVE-2025-2953 torch: PyTorch torch.mkldnn_max_pool2d denial of service
    space/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 ...
    space/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 ...
    space/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ⓘ 94 found · 3 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-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2026-5241). Fix: Update that package to its patched version.
  • Serious PYSEC-2026-2102 AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, the C parser (the default for most installs) accepted null bytes and control characters in resp
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2026-34520). Fix: Update that package to its patched version.
  • Serious PYSEC-2026-457 Arbitrary Code Execution in Pillow
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2023-50447). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2178 Gradio before version 6.15.0 contains a cookie injection vulnerability that allows remote attackers to perform cross-Space session fixation by exploiting a shared module-level HTTP client used across
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2026-48545). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-2179 Gradio before 6.16.0 contain a path traversal vulnerability in the FileExplorer component's preprocess() method that allows unauthenticated attackers to escape the configured root directory by supplyi
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2026-49119). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-191 A vulnerability, which was classified as problematic, has been found in PyTorch 2.6.0+cu124. Affected by this issue is the function torch.mkldnn_max_pool2d. The manipulation leads to denial of service
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-2953). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-198 In PyTorch through 2.6.0, when eager is used, nn.PairwiseDistance(p=2) produces incorrect results.
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-46148). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-199 In PyTorch before 2.7.0, when inductor is used, nn.Fold has an assertion error.
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-46149). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-200 In PyTorch before 2.7.0, when torch.compile is used, FractionalMaxPool2d has inconsistent results.
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-46150). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-201 In PyTorch before 2.7.0, bitwise_right_shift produces incorrect output for certain out-of-bounds values of the "other" argument.
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-46152). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-202 PyTorch before 3.7.0 has a bernoulli_p decompose function in decompositions.py even though it lacks full consistency with the eager CPU implementation, negatively affecting nn.Dropout1d, nn.Dropout2d,
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-46153). Fix: Update that package to its patched version.
  • 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-24712050-521e-42bc-96ab-37824483965f/space/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-24712050-521e-42bc-96ab-37824483965f/space/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-205 A syntax error in the component proxy_tensor.py of pytorch v2.7.0 allows attackers to cause a Denial of Service (DoS).
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-55553). 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-24712050-521e-42bc-96ab-37824483965f/space/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-2025-207 A Name Error occurs in pytorch v2.7.0 when a PyTorch model consists of torch.cummin and is compiled by Inductor, leading to a Denial of Service (DoS).
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-55557). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-208 A buffer overflow occurs in pytorch v2.7.0 when a PyTorch model consists of torch.nn.Conv2d, torch.nn.functional.hardshrink, and torch.Tensor.view-torch.mv() and is compiled by Inductor, leading to a
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-55558). Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2025-209 An issue in pytorch v2.7.0 can lead to a Denial of Service (DoS) when a PyTorch model consists of torch.Tensor.to_sparse() and torch.Tensor.to_dense() and is compiled by Inductor.
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-55560). 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-24712050-521e-42bc-96ab-37824483965f/space/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-1970 PyTorch Improper Resource Shutdown or Release vulnerability
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/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 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-24712050-521e-42bc-96ab-37824483965f/space/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-c678-jfcj-6jmf PyTorch Tuple Handler is Vulnerable to Memory Corruption through Manipulation of None Argument
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-2148). Fix: Update that package to its patched version.
  • Worth fixing GHSA-f4hp-rmr7-r7v8 PyTorch is Vulnerable to Memory Consumption through pad_packed_sequence Function
    /workdirs/scan-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-2998). 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-24712050-521e-42bc-96ab-37824483965f/space/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-24712050-521e-42bc-96ab-37824483965f/space/requirements.txt
    A package you depend on has a known security hole (CVE-2025-3000). Fix: Update that package to its patched version.
… 69 more not shown

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.