gitsafehub
github.com/kailun-qin/svsm ↗

kailun-qin/svsm

scanned 2026-08-14 · git a85214b
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 secretsVulnerable dependencies3Known OSS vulnerabilities6Risky code patternsMalicious dependenciesProject 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-2026-25541 Bytes is a utility library for working with bytes. From version 1.2.1 ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2026-25541). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-55159 slab: Slab: Out-of-bounds Memory Access Vulnerability
    Cargo.lock
    A package you depend on has a known security hole (CVE-2025-55159). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-25727 time: time affected by a stack exhaustion denial of service attack
    Cargo.lock
    A package you depend on has a known security hole (CVE-2026-25727). 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-0007 Integer overflow in `BytesMut::reserve`
    /workdirs/scan-b50032d6-8e10-47aa-b5d4-169fa1b2bbaf/Cargo.lock
    A package you depend on has a known security hole (CVE-2026-25541). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2025-0047 Out-of-bounds access in `get_disjoint_mut` due to incorrect bounds check
    /workdirs/scan-b50032d6-8e10-47aa-b5d4-169fa1b2bbaf/Cargo.lock
    A package you depend on has a known security hole (CVE-2025-55159). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2026-0009 Denial of Service via Stack Exhaustion
    /workdirs/scan-b50032d6-8e10-47aa-b5d4-169fa1b2bbaf/Cargo.lock
    A package you depend on has a known security hole (CVE-2026-25727). Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0190 Unsoundness in `Error::downcast_mut()`
    /workdirs/scan-b50032d6-8e10-47aa-b5d4-169fa1b2bbaf/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0186 Unchecked pointer offset in crate `memmap2`
    /workdirs/scan-b50032d6-8e10-47aa-b5d4-169fa1b2bbaf/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-b50032d6-8e10-47aa-b5d4-169fa1b2bbaf/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.