gitsafehub
github.com/mic92/vmsh ↗

mic92/vmsh

scanned 2026-08-10 · git dd39175
3 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 secrets3Vulnerable dependencies3Known OSS vulnerabilities4Risky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks 3 found · 3 serious

API keys, passwords or tokens committed into the repo.

  • Serious private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    nix/ssh_key:1
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    nix/ssh_key:1
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Serious private-key Identified a Private Key, which may compromise cryptographic security and sensitive data encryption.
    nix/ssh_key:1
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivy 3 found

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

  • Worth fixing CVE-2023-50711 vmm-sys-util is a collection of modules that provides helpers and util ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2023-50711). Fix: Update that package to its patched version.
  • Worth fixing GHSA-9cc5-2pq7-hfj8 xmas-elf potential out-of-bounds read with a malformed ELF file and the HashTable API.
    Cargo.lock
    A package you depend on has a known security hole (GHSA-9cc5-2pq7-hfj8). Fix: Update that package to its patched version.
  • Minor CVE-2023-41051 In a typical Virtual Machine Monitor (VMM) there are several component ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2023-41051). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 4 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing RUSTSEC-2024-0002 `serde` deserialization for `FamStructWrapper` lacks bound checks that could potentially lead to out-of-bounds memory access
    /workdirs/scan-a0ac2c37-22c2-4b17-8284-0cf33d9d78f1/Cargo.lock
    A package you depend on has a known security hole (CVE-2023-50711). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2025-0018 Potential out-of-bounds read with a malformed ELF file and the HashTable API.
    /workdirs/scan-a0ac2c37-22c2-4b17-8284-0cf33d9d78f1/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Minor RUSTSEC-2023-0056 Default functions in VolatileMemory trait lack bounds checks, potentially leading to out-of-bounds memory accesses
    /workdirs/scan-a0ac2c37-22c2-4b17-8284-0cf33d9d78f1/Cargo.lock
    A package you depend on has a known security hole (CVE-2023-41051). Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0383 bcc is unmaintained
    /workdirs/scan-a0ac2c37-22c2-4b17-8284-0cf33d9d78f1/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.