gitsafehub
github.com/hatoo/raytracing-1w ↗

hatoo/raytracing-1w

scanned 2026-08-13 · git 06f6787
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 secretsVulnerable dependencies3Known OSS vulnerabilities7Risky 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 · 1 serious

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

  • Serious CVE-2021-32810 rust-crossbeam-deque: race condition may lead to double free
    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 CVE-2022-23639 crossbeam-utils provides atomics, synchronization primitives, scoped t ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2022-23639). Fix: Update that package to its patched version.
  • Minor GHSA-cq8v-f236-94qc Rand is unsound with a custom logger using rand::rng()
    Cargo.lock
    A package you depend on has a known security hole (GHSA-cq8v-f236-94qc). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 7 found · 1 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious RUSTSEC-2021-0093 Data race in crossbeam-deque
    /workdirs/scan-2d293c83-71a7-4305-9edf-8150c4fbd7f3/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-2022-0041 Unsoundness of AtomicCell<*64> arithmetics on 32-bit targets that support Atomic*64
    /workdirs/scan-2d293c83-71a7-4305-9edf-8150c4fbd7f3/Cargo.lock
    A package you depend on has a known security hole (CVE-2022-23639). Fix: Update that package to its patched version.
  • FYI RUSTSEC-2025-0056 adler crate is unmaintained, use adler2 instead
    /workdirs/scan-2d293c83-71a7-4305-9edf-8150c4fbd7f3/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0196 `cgmath` is unmaintained
    /workdirs/scan-2d293c83-71a7-4305-9edf-8150c4fbd7f3/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0197 `Matrix{2,3,4}::swap_columns` can trigger undefined behavior for identical indices
    /workdirs/scan-2d293c83-71a7-4305-9edf-8150c4fbd7f3/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0204 Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
    /workdirs/scan-2d293c83-71a7-4305-9edf-8150c4fbd7f3/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0097 Rand is unsound with a custom logger using `rand::rng()`
    /workdirs/scan-2d293c83-71a7-4305-9edf-8150c4fbd7f3/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.