Is tokio-io-timeout safe to use?

tokio-io-timeout has no known vulnerabilities on the latest version (1.2.1). DepScope rates its health at 67/100 (moderate risk).

What is the latest version of tokio-io-timeout?

The latest version of tokio-io-timeout is 1.2.1, released 2025-07-20.

Does tokio-io-timeout have known vulnerabilities?

No known vulnerabilities on the latest version of tokio-io-timeout.

Is tokio-io-timeout deprecated?

No, tokio-io-timeout is actively maintained. Latest release: 1.2.1 (2025-07-20).

What are alternatives to tokio-io-timeout?

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

What license does tokio-io-timeout use?

tokio-io-timeout is licensed under MIT/Apache-2.0.

tokio-io-timeout

cargov1.2.1

Tokio wrappers which apply timeouts to IO operations

License MIT/Apache-2.0permissive18 versions0 deps14,266,072 weekly dl

sfackler/tokio-io-timeout

/ 100

Health

safe to use

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

Health breakdown0 – 100

10/25

maintenance

20/20

popularity

25/25

security

12/15

maturity

0/15

community

Vulnerabilities

none known

Maintainer trust

Active maintainers (3m)

1

Contributors (12m)

1

Primary author dominance

100%

GitHub stars

43

single active maintainer 3msingle author dominance

Quality signals

OSS Criticality

0.72critical

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cargo/tokio-io-timeout