Is oxide-tokio-rt safe to use?

oxide-tokio-rt has no known vulnerabilities on the latest version (0.1.4). DepScope rates its health at 63/100 (moderate risk).

What is the latest version of oxide-tokio-rt?

The latest version of oxide-tokio-rt is 0.1.4, released 2026-04-15.

Does oxide-tokio-rt have known vulnerabilities?

No known vulnerabilities on the latest version of oxide-tokio-rt.

Is oxide-tokio-rt deprecated?

No, oxide-tokio-rt is actively maintained. Latest release: 0.1.4 (2026-04-15).

What are alternatives to oxide-tokio-rt?

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

What license does oxide-tokio-rt use?

oxide-tokio-rt is licensed under MPL-2.0.

oxide-tokio-rt

cargov0.1.4

Shared Tokio runtime configuration for production Oxide software

License MPL-2.0weak copyleft5 versions0 deps48,487 weekly dl

oxidecomputer/oxide-tokio-rt

/ 100

Health

use with caution

[email protected] low health (63/100) — consider alternatives

Moderate health score (63/100) — verify manually

Health breakdown0 – 100

25/25

maintenance

10/20

popularity

25/25

security

3/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/oxide-tokio-rt

oxide-tokio-rt

cargov0.1.4

Shared Tokio runtime configuration for production Oxide software

License MPL-2.0weak copyleft5 versions0 deps48,487 weekly dl

oxidecomputer/oxide-tokio-rt

/ 100

Health

use with caution

[email protected] low health (63/100) — consider alternatives

Moderate health score (63/100) — verify manually

Health breakdown0 – 100

25/25

maintenance

10/20

popularity

25/25

security

3/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/oxide-tokio-rt