Is unsafe-libyaml safe to use?

unsafe-libyaml has no known vulnerabilities on the latest version (0.2.11). DepScope rates its health at 54/100 (high risk).

What is the latest version of unsafe-libyaml?

The latest version of unsafe-libyaml is 0.2.11, released 2024-03-17.

No known vulnerabilities on the latest version of unsafe-libyaml.

No, unsafe-libyaml is actively maintained. Latest release: 0.2.11 (2024-03-17).

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

unsafe-libyaml is licensed under MIT.

cargov0.2.11

libyaml transpiled to rust by c2rust

License MITpermissive17 versions0 deps44,434,638 weekly dl

/ 100

Health

safe to use

[email protected] is safe to use (health: 54/100)

Health breakdown0 – 100

0/25

maintenance

20/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Maintainer trust

Active maintainers (3m)

1

Contributors (12m)

0

Primary author dominance

0%

GitHub stars

35

single active maintainer 3marchived repo

Quality signals

OSS Criticality

0.69high

Download trend

stable(0%)

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cargo/unsafe-libyaml