Is utf8-tokio safe to use?

utf8-tokio has no known vulnerabilities on the latest version (0.2.1). DepScope rates its health at 42/100 (high risk).

What is the latest version of utf8-tokio?

The latest version of utf8-tokio is 0.2.1, released 2024-06-20.

Does utf8-tokio have known vulnerabilities?

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

Is utf8-tokio deprecated?

No, utf8-tokio is actively maintained. Latest release: 0.2.1 (2024-06-20).

What are alternatives to utf8-tokio?

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

What license does utf8-tokio use?

utf8-tokio is licensed under Apache-2.0 WITH LLVM-exception.

utf8-tokio

cargov0.2.1

Streaming UTF-8 codec based on Tokio

License Apache-2.0 WITH LLVM-exception4 versions0 deps7,414 weekly dl

wrpc/wasm-tokio

/ 100

Health

safe to use

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

Health breakdown0 – 100

5/25

maintenance

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