Is elicit_tokio safe to use?

elicit_tokio has no known vulnerabilities on the latest version (0.10.0). DepScope rates its health at 50/100 (high risk).

What is the latest version of elicit_tokio?

The latest version of elicit_tokio is 0.10.0, released 2026-04-05.

Does elicit_tokio have known vulnerabilities?

No known vulnerabilities on the latest version of elicit_tokio.

Is elicit_tokio deprecated?

No, elicit_tokio is actively maintained. Latest release: 0.10.0 (2026-04-05).

What are alternatives to elicit_tokio?

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

What license does elicit_tokio use?

elicit_tokio is licensed under Apache-2.0 OR MIT.

elicit_tokio

cargov0.10.0

Elicitation-enabled tokio shadow crate — MCP tools for async time, sync primitives, and runtime inspection

License Apache-2.0 OR MITpermissive1 versions0 deps29 weekly dl

crumplecup/elicitation

/ 100

Health

safe to use

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

Health breakdown0 – 100

25/25

maintenance

0/20

popularity

25/25

security

0/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/elicit_tokio

elicit_tokio

cargov0.10.0

Elicitation-enabled tokio shadow crate — MCP tools for async time, sync primitives, and runtime inspection

License Apache-2.0 OR MITpermissive1 versions0 deps29 weekly dl

crumplecup/elicitation

/ 100

Health

safe to use

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

Health breakdown0 – 100

25/25

maintenance

0/20

popularity

25/25

security

0/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/elicit_tokio