Is ggml-sys-bleedingedge safe to use?

ggml-sys-bleedingedge has no known vulnerabilities on the latest version (2404291813.0.0+llamacpp-release.b2757). DepScope rates its health at 43/100 (high risk).

What is the latest version of ggml-sys-bleedingedge?

The latest version of ggml-sys-bleedingedge is 2404291813.0.0+llamacpp-release.b2757, released 2024-04-29.

Does ggml-sys-bleedingedge have known vulnerabilities?

No known vulnerabilities on the latest version of ggml-sys-bleedingedge.

Is ggml-sys-bleedingedge deprecated?

No, ggml-sys-bleedingedge is actively maintained. Latest release: 2404291813.0.0+llamacpp-release.b2757 (2024-04-29).

What are alternatives to ggml-sys-bleedingedge?

Popular alternatives to ggml-sys-bleedingedge in Cargo include: hashbrown, getrandom, windows-sys, syn, rand_core.

What license does ggml-sys-bleedingedge use?

ggml-sys-bleedingedge is licensed under MIT.

ggml-sys-bleedingedge

cargov2404291813.0.0+llamacpp-release.b2757

Bleeding edge low-level bindings to GGML.

License MITpermissive493 versions0 deps566 weekly dl

KerfuffleV2/ggml-sys-bleedingedge

/ 100

Health

safe to use

[email protected]+llamacpp-release.b2757 is safe to use (health: 43/100)

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

15/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cargo/ggml-sys-bleedingedge