gitsafehub
github.com/jannic/condure ↗

jannic/condure

scanned 2026-08-12 · git d0569b1
2 of 6 checks flagged a security issue
🔴 Needs attention
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 vulnerabilities15Risky 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 CVE-2020-35711 An issue has been discovered in the arc-swap crate before 0.4.8 (and 1 ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35711). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-35919 An issue was discovered in the net2 crate before 0.2.36 for Rust. It h ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35919). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-35920 An issue was discovered in the socket2 crate before 0.3.16 for Rust. I ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35920). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-26235 Segmentation fault in time
    Cargo.lock
    A package you depend on has a known security hole (CVE-2020-26235). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

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

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious RUSTSEC-2021-0093 Data race in crossbeam-deque
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole (CVE-2021-32810). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2020-0091 Dangling reference in `access::Map` with Constant
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35711). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2022-0041 Unsoundness of AtomicCell<*64> arithmetics on 32-bit targets that support Atomic*64
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole (CVE-2022-23639). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2020-0080 `miow` invalidly assumes the memory layout of std::net::SocketAddr
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35921). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2020-0078 `net2` invalidly assumes the memory layout of std::net::SocketAddr
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35919). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2022-0013 Regexes with large repetitions on empty sub-expressions take a very long time to parse
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole (CVE-2022-24713). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2020-0071 Potential segfault in the time crate
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole (CVE-2020-26235). Fix: Update that package to its patched version.
  • FYI RUSTSEC-2021-0139 ansi_term is Unmaintained
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2021-0145 Potential unaligned read
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0375 `atty` is unmaintained
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2022-0078 Use-after-free due to a lifetime error in `Vec::into_iter()`
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2023-0045 memoffset allows reading uninitialized memory
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2020-0016 `net2` crate has been deprecated; use `socket2` instead
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2021-0127 serde_cbor is unmaintained
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2020-0163 `term_size` is unmaintained; use `terminal_size` instead
    /workdirs/scan-4a03c461-5e35-4892-854c-249605bb959d/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.