gitsafehub
github.com/akavel/care ↗

akavel/care

scanned 2026-08-06 · git 8d5ac2e
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 dependencies3Known 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ⓘ 3 found

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

  • Worth fixing CVE-2024-12224 idna: idna accepts Punycode labels that do not produce any non-ASCII when decoded
    Cargo.lock
    A package you depend on has a known security hole (CVE-2024-12224). Fix: Update that package to its patched version.
  • Minor GHSA-j39j-6gw9-jw6h git2 has potential undefined behavior when dereferencing Buf struct
    Cargo.lock
    A package you depend on has a known security hole (GHSA-j39j-6gw9-jw6h). 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

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing RUSTSEC-2024-0421 `idna` accepts Punycode labels that do not produce any non-ASCII when decoded
    /workdirs/scan-5bba0afe-8b59-4cfd-9112-0318bd9fa50b/Cargo.lock
    A package you depend on has a known security hole (CVE-2024-12224). Fix: Update that package to its patched version.
  • Minor RUSTSEC-2026-0008 Potential undefined behavior when dereferencing Buf struct
    /workdirs/scan-5bba0afe-8b59-4cfd-9112-0318bd9fa50b/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0190 Unsoundness in `Error::downcast_mut()`
    /workdirs/scan-5bba0afe-8b59-4cfd-9112-0318bd9fa50b/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0183 Potential undefined behavior when calling Remote::list()
    /workdirs/scan-5bba0afe-8b59-4cfd-9112-0318bd9fa50b/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2026-0184 Potential undefined behavior with Signature from a buffer-created BlameHunk
    /workdirs/scan-5bba0afe-8b59-4cfd-9112-0318bd9fa50b/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-5bba0afe-8b59-4cfd-9112-0318bd9fa50b/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-5bba0afe-8b59-4cfd-9112-0318bd9fa50b/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.