gitsafehub
github.com/abdelstark/cairo-rs ↗

abdelstark/cairo-rs

scanned 2026-08-06 · git ef1923d
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 vulnerabilities23Risky 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 GHSA-g23h-7vf9-xc25 Mimalloc Can Allocate Memory with Bad Alignment
    Cargo.lock
    A package you depend on has a known security hole (GHSA-g23h-7vf9-xc25). Fix: Update that package to its patched version.
  • Minor GHSA-3288-p39f-rqpv Unsoundness in opt-in ARMv8 assembly backend for `keccak`
    Cargo.lock
    A package you depend on has a known security hole (GHSA-3288-p39f-rqpv). 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ⓘ 23 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing RUSTSEC-2022-0094 Mimalloc Can Allocate Memory with Bad Alignment
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing RUSTSEC-2022-0094 Mimalloc Can Allocate Memory with Bad Alignment
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/custom_hint_example/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Minor RUSTSEC-2026-0012 Unsoundness in opt-in ARMv8 assembly backend for `keccak`
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Minor RUSTSEC-2026-0012 Unsoundness in opt-in ARMv8 assembly backend for `keccak`
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/custom_hint_example/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-e91b3ce0-059a-41e6-8318-e00a7ef8be25/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-e91b3ce0-059a-41e6-8318-e00a7ef8be25/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2025-0141 Bincode is unmaintained
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/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-e91b3ce0-059a-41e6-8318-e00a7ef8be25/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0388 `derivative` is unmaintained; consider using an alternative
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/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-e91b3ce0-059a-41e6-8318-e00a7ef8be25/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0436 paste - no longer maintained
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0370 proc-macro-error is unmaintained
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/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-e91b3ce0-059a-41e6-8318-e00a7ef8be25/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2023-0018 Race Condition Enabling Link Following and Time-of-check Time-of-use (TOCTOU)
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2021-0127 serde_cbor is unmaintained
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/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-e91b3ce0-059a-41e6-8318-e00a7ef8be25/custom_hint_example/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-e91b3ce0-059a-41e6-8318-e00a7ef8be25/custom_hint_example/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2025-0141 Bincode is unmaintained
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/custom_hint_example/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2022-0078 Use-after-free due to a lifetime error in `Vec::into_iter()`
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/custom_hint_example/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0388 `derivative` is unmaintained; consider using an alternative
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/custom_hint_example/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0436 paste - no longer maintained
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/custom_hint_example/Cargo.lock
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • FYI RUSTSEC-2024-0370 proc-macro-error is unmaintained
    /workdirs/scan-e91b3ce0-059a-41e6-8318-e00a7ef8be25/custom_hint_example/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-e91b3ce0-059a-41e6-8318-e00a7ef8be25/custom_hint_example/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.