gitsafehub
github.com/iogamaster/swww ↗

iogamaster/swww

scanned 2026-08-11 · git 344ffda
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 secrets✓Vulnerable dependencies5Known OSS vulnerabilities12Risky 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ⓘ 5 found

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

  • Worth fixing GHSA-2rxc-gjrp-vjhx Unsoundness in anstream
    Cargo.lock
    A package you depend on has a known security hole (GHSA-2rxc-gjrp-vjhx). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-43806 Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `r ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2024-43806). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-43806 Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `r ...
    Cargo.lock
    A package you depend on has a known security hole (CVE-2024-43806). 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.
  • 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ⓘ 12 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing RUSTSEC-2026-0194 Quadratic run time when checking a start tag for duplicate attribute names
    /workdirs/scan-55fd9970-2348-43ef-92f3-fb74fddf77fe/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2026-0195 Unbounded namespace-declaration allocation in `NsReader` enables memory-exhaustion denial of service
    /workdirs/scan-55fd9970-2348-43ef-92f3-fb74fddf77fe/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-c827-hfw6-qwvm rustix's `rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion
    /workdirs/scan-55fd9970-2348-43ef-92f3-fb74fddf77fe/Cargo.lock
    A package you depend on has a known security hole (CVE-2024-43806). Fix: Update that package to its patched version.
  • Worth fixing GHSA-c827-hfw6-qwvm rustix's `rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion
    /workdirs/scan-55fd9970-2348-43ef-92f3-fb74fddf77fe/Cargo.lock
    A package you depend on has a known security hole (CVE-2024-43806). Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2026-0009 Denial of Service via Stack Exhaustion
    /workdirs/scan-55fd9970-2348-43ef-92f3-fb74fddf77fe/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-2025-0056 adler crate is unmaintained, use adler2 instead
    /workdirs/scan-55fd9970-2348-43ef-92f3-fb74fddf77fe/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0404 Unsoundness in anstream
    /workdirs/scan-55fd9970-2348-43ef-92f3-fb74fddf77fe/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-55fd9970-2348-43ef-92f3-fb74fddf77fe/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-55fd9970-2348-43ef-92f3-fb74fddf77fe/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-55fd9970-2348-43ef-92f3-fb74fddf77fe/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0001 Potential Undefined Behaviors in `Arc<T>`/`Rc<T>` impls of `from_value` on OOM
    /workdirs/scan-55fd9970-2348-43ef-92f3-fb74fddf77fe/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0235 Insufficient archive validation can cause out-of-bounds reads in archives containing Rc/Arc
    /workdirs/scan-55fd9970-2348-43ef-92f3-fb74fddf77fe/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.