gitsafehub
github.com/chenxu0602/optrush ↗

chenxu0602/optrush

scanned 2026-08-06 · git bf473f7
2 of 6 checks flagged a security issue
🟡 Worth a look
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets✓Vulnerable dependencies4Known OSS vulnerabilities6Risky 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ⓘ 4 found

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

  • Worth fixing GHSA-36hh-v3qg-5jq4 PyO3 has an Out-of-bounds Read in `nth` / `nth_back` for `PyList` and `PyTuple` iterators
    Cargo.lock
    A package you depend on has a known security hole (GHSA-36hh-v3qg-5jq4). Fix: Update that package to its patched version.
  • Worth fixing GHSA-chgr-c6px-7xpp PyO3 has a missing `Sync` bound on `PyCFunction::new_closure` closures
    Cargo.lock
    A package you depend on has a known security hole (GHSA-chgr-c6px-7xpp). Fix: Update that package to its patched version.
  • Minor GHSA-pph8-gcv7-4qj5 PyO3 Risk of buffer overflow in `PyString::from_object`
    Cargo.lock
    A package you depend on has a known security hole (GHSA-pph8-gcv7-4qj5). Fix: Update that package to its patched version.
  • Minor GHSA-cq8v-f236-94qc Rand is unsound with a custom logger using rand::rng()
    Cargo.lock
    A package you depend on has a known security hole (GHSA-cq8v-f236-94qc). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 6 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing RUSTSEC-2026-0177 Missing `Sync` bound on `PyCFunction::new_closure` closures
    /workdirs/scan-3de0a439-c5ac-4fb8-9be3-f15a93722e8b/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-36hh-v3qg-5jq4 PyO3 has an Out-of-bounds Read in `nth` / `nth_back` for `PyList` and `PyTuple` iterators
    /workdirs/scan-3de0a439-c5ac-4fb8-9be3-f15a93722e8b/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing PYSEC-2026-1845 pytest has vulnerable tmpdir handling
    /workdirs/scan-3de0a439-c5ac-4fb8-9be3-f15a93722e8b/uv.lock
    A package you depend on has a known security hole (CVE-2025-71176). Fix: Update that package to its patched version.
  • Minor RUSTSEC-2025-0020 Risk of buffer overflow in `PyString::from_object`
    /workdirs/scan-3de0a439-c5ac-4fb8-9be3-f15a93722e8b/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0436 paste - no longer maintained
    /workdirs/scan-3de0a439-c5ac-4fb8-9be3-f15a93722e8b/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0097 Rand is unsound with a custom logger using `rand::rng()`
    /workdirs/scan-3de0a439-c5ac-4fb8-9be3-f15a93722e8b/Cargo.lock
    A package you depend on has a known security hole. 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.