gitsafehub
github.com/gfx-rs/portability ↗

gfx-rs/portability

scanned 2026-08-11 · git 6d55421
2 of 6 checks flagged a security issue
🔴 Needs attention
Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secretsVulnerable dependencies5Known OSS vulnerabilities13Risky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks timed out

API keys, passwords or tokens committed into the repo.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via Gitleaks v8.21.2 · MIT

error: timeout after 120s

Vulnerable dependencies — Trivy 5 found

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

  • Worth fixing CVE-2020-35910 An issue was discovered in the lock_api crate before 0.4.2 for Rust. A ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35910). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-35911 An issue was discovered in the lock_api crate before 0.4.2 for Rust. A ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35911). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-35912 An issue was discovered in the lock_api crate before 0.4.2 for Rust. A ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35912). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-35913 An issue was discovered in the lock_api crate before 0.4.2 for Rust. A ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35913). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-35914 An issue was discovered in the lock_api crate before 0.4.2 for Rust. A ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35914). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 13 found · 2 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious RUSTSEC-2021-0090 Reading on uninitialized memory may cause UB ( `util::read_spv()` )
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/Cargo.lock
    A package you depend on has a known security hole (CVE-2021-45688). Fix: Update that package to its patched version.
  • Serious RUSTSEC-2021-0091 Reading on uninitialized buffer may cause UB ( `gfx_auxil::read_spirv()` )
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/Cargo.lock
    A package you depend on has a known security hole (CVE-2021-45689). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2020-0070 Some lock_api lock guard objects can cause data races
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/Cargo.lock
    A package you depend on has a known security hole (CVE-2020-35910). Fix: Update that package to its patched version.
  • FYI RUSTSEC-2025-0056 adler crate is unmaintained, use adler2 instead
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/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-8c9b6347-feda-46bd-844f-a46191bbb043/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-8c9b6347-feda-46bd-844f-a46191bbb043/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2025-0057 fxhash - no longer maintained
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0384 `instant` is unmaintained
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2020-0077 memmap is unmaintained
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2021-0140 rusttype is Unmaintained
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2021-0140 rusttype is Unmaintained
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2021-0096 spirv_headers is unmaintained, use spirv instead
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2020-0020 `stb_truetype` crate has been deprecated; use `ttf-parser` instead
    /workdirs/scan-8c9b6347-feda-46bd-844f-a46191bbb043/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.