gitsafehub
github.com/infeo/dokany-nio-adapter ↗

infeo/dokany-nio-adapter

scanned 2026-08-11 · git 858c085
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 dependencies4Known OSS vulnerabilities6Risky 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ⓘ 4 found

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

  • Worth fixing CVE-2023-2976 guava: insecure temporary directory creation
    pom.xml
    A package you depend on has a known security hole (CVE-2023-2976). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-47554 apache-commons-io: Possible denial of service attack on untrusted input to XmlStreamReader
    pom.xml
    A package you depend on has a known security hole (CVE-2024-47554). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-29425 apache-commons-io: Limited path traversal in Apache Commons IO 2.2 to 2.6
    pom.xml
    A package you depend on has a known security hole (CVE-2021-29425). Fix: Update that package to its patched version.
  • Minor CVE-2020-8908 guava: local information disclosure via temporary directory created with unsafe permissions
    pom.xml
    A package you depend on has a known security hole (CVE-2020-8908). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 6 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-7g45-4rm6-3mm3 Guava vulnerable to insecure use of temporary directory
    /workdirs/scan-c49b4b6b-d03c-486d-a1b8-edb3191b317d/pom.xml
    A package you depend on has a known security hole (CVE-2023-2976). Fix: Update that package to its patched version.
  • Worth fixing GHSA-78wr-2p64-hpwj Apache Commons IO: Possible denial of service attack on untrusted input to XmlStreamReader
    /workdirs/scan-c49b4b6b-d03c-486d-a1b8-edb3191b317d/pom.xml
    A package you depend on has a known security hole (CVE-2024-47554). Fix: Update that package to its patched version.
  • Worth fixing GHSA-gwrp-pvrq-jmwv Path Traversal and Improper Input Validation in Apache Commons IO
    /workdirs/scan-c49b4b6b-d03c-486d-a1b8-edb3191b317d/pom.xml
    A package you depend on has a known security hole (CVE-2021-29425). Fix: Update that package to its patched version.
  • Worth fixing GHSA-269g-pwp5-87pp TemporaryFolder on unix-like systems does not limit access to created files
    /workdirs/scan-c49b4b6b-d03c-486d-a1b8-edb3191b317d/pom.xml
    A package you depend on has a known security hole (CVE-2020-15250). Fix: Update that package to its patched version.
  • Worth fixing GHSA-4jrv-ppp4-jm57 Deserialization of Untrusted Data in Gson
    /workdirs/scan-c49b4b6b-d03c-486d-a1b8-edb3191b317d/pom.xml
    A package you depend on has a known security hole (CVE-2022-25647). Fix: Update that package to its patched version.
  • Minor GHSA-5mg8-w23w-74h3 Information Disclosure in Guava
    /workdirs/scan-c49b4b6b-d03c-486d-a1b8-edb3191b317d/pom.xml
    A package you depend on has a known security hole (CVE-2020-8908). 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.