Is readlock-tokio safe to use?

readlock-tokio has no known vulnerabilities on the latest version (0.1.6). DepScope rates its health at 65/100 (moderate risk).

What is the latest version of readlock-tokio?

The latest version of readlock-tokio is 0.1.6, released 2026-02-06.

Does readlock-tokio have known vulnerabilities?

No known vulnerabilities on the latest version of readlock-tokio.

Is readlock-tokio deprecated?

No, readlock-tokio is actively maintained. Latest release: 0.1.6 (2026-02-06).

What are alternatives to readlock-tokio?

Popular alternatives to readlock-tokio in Cargo include: hashbrown, getrandom, windows-sys, syn.

What license does readlock-tokio use?

readlock-tokio is licensed under MPL-2.0.

readlock-tokio

cargov0.1.6

A weird alternative to Arc<RwLock<T>>, using tokio's RwLock

License MPL-2.0weak copyleft7 versions0 deps157,951 weekly dl

https://codeberg.org/jplatte/readlock

/ 100

Health

safe to use

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

Health breakdown0 – 100

20/25

maintenance

14/20

popularity

25/25

security

6/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/readlock-tokio