gitsafehub
github.com/robloach/libretro-lutro ↗

robloach/libretro-lutro

scanned 2026-08-12 · git a841c46
1 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 dependencies✓Known OSS vulnerabilities7Risky 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ⓘ none found ✓

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

Nothing found by this check. ✓

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 7 found · 3 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious CVE-2020-27304 The CivetWeb web library does not validate uploaded filepaths when running on an OS other than Windows, when using the built-in HTTP form-based file upload mechanism, via the mg_handle_form_request AP
    /workdirs/scan-f6c5416a-b945-4c4a-a455-70d0078c0682/deps/lua
    A package you depend on has a known security hole (CVE-2020-27304). Fix: Update that package to its patched version.
  • Serious CVE-2019-19391 In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a type confusion issue that leads to arbitrary memory write or read operations, because certain cases inv
    /workdirs/scan-f6c5416a-b945-4c4a-a455-70d0078c0682/deps/luajit
    A package you depend on has a known security hole (CVE-2019-19391). Fix: Update that package to its patched version.
  • Serious CVE-2024-25178 LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an out-of-bounds read in the stack-overflow handler in lj_state.c.
    /workdirs/scan-f6c5416a-b945-4c4a-a455-70d0078c0682/deps/luajit
    A package you depend on has a known security hole (CVE-2024-25178). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-12684 Out-of-bounds Read in the send_ssi_file function in civetweb.c in CivetWeb through 1.10 allows attackers to cause a Denial of Service or Information Disclosure via a crafted SSI file.
    /workdirs/scan-f6c5416a-b945-4c4a-a455-70d0078c0682/deps/lua
    A package you depend on has a known security hole (CVE-2018-12684). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-15890 LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled.
    /workdirs/scan-f6c5416a-b945-4c4a-a455-70d0078c0682/deps/luajit
    A package you depend on has a known security hole (CVE-2020-15890). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-24372 LuaJIT through 2.1.0-beta3 has an out-of-bounds read in lj_err_run in lj_err.c.
    /workdirs/scan-f6c5416a-b945-4c4a-a455-70d0078c0682/deps/luajit
    A package you depend on has a known security hole (CVE-2020-24372). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-25177 LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an unsinking of IR_FSTORE for NULL metatable, which leads to Denial of Service (DoS).
    /workdirs/scan-f6c5416a-b945-4c4a-a455-70d0078c0682/deps/luajit
    A package you depend on has a known security hole (CVE-2024-25177). 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.