cargo package report

Is stack-graphs safe?

2 known vulnerabilities.

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so cargo packages are not covered.

      cvss
      not scored

      severity out of 10

      epss
      not scored

      chance of exploitation in 30 days

      xyz score
      not scored

      CyberXYZ composite out of 10

      fig. 01 — RUSTSEC-2026-0302, the advisory selected below

      // 2 advisories

      RUSTSEC-2026-0302

      UNKNOWN

      stackgraphs::c is a public module. From 0.0.3 through the current crates.io release 0.14.1, its pointer-taking entry points are pub extern "C" fn rather than unsafe fn. Safe Rust can call them.

      sgstackgraphfree frees the pointer with Box::fromraw. sgstackgraphfree(std::ptr::nullmut()) is immediate undefined behavior. The same shape is used by the other free exports and by getters and mutators that dereference the caller-supplied pointer or pass it to fromrawparts (sgstackgraphnodes, sgstackgraphaddedges, and the rest of the pointer-taking functions in src/c.rs). Constructors that take no pointer are not part of this issue.

      The upstream repository is archived, so a fix cannot be filed there and no patched release exists. The soundness fix is to make every pointer-taking export unsafe extern "C" fn, with a safety comment that the pointer is non-null and, for free, came from the matching constructor.

      Checked 2026-09-24 at 08:33 UTC. The most recent advisory here was published 2026-09-22. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.
      Is stack-graphs safe? cargo package security report | CyberXYZ