cargo package report

Is slice-ring-buffer safe?

1 known vulnerability.

cvss

not scored

how bad it is if exploited, out of 10

epss

not scored

chance of exploitation in the next 30 days

xyz score

3.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-7mcq-f592-pf7v, the advisory selected below

// advisories

GHSA-7mcq-f592-pf7v

UNKNOWN

The crate [slice-ring-buffer](https://crates.io/crates/slice-ring-buffer) was developed as a fork of [slice-deque](https://crates.io/crates/slice-deque) to continue maintenance and provide security patches, since the latter has been officially unmaintained ([RUSTSEC-2020-0158](https://rustsec.org/advisories/RUSTSEC-2020-0158.html)).

Affected: >=0.0.0-0
Fixed in: not stated
Weakness: CWE-415
Published: 2025-07-16
Source: github

GHSA

// dependencies

0 direct

// ai model usage

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

Checked 2026-09-22 at 01:32 UTC. The most recent advisory here was published 2025-07-16. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Is slice-ring-buffer safe? cargo package security report | CyberXYZ