Is futures-cpupool safe to use?

futures-cpupool has no known vulnerabilities on the latest version (0.1.8). DepScope rates its health at 51/100 (high risk).

What is the latest version of futures-cpupool?

The latest version of futures-cpupool is 0.1.8, released 2018-01-02.

Does futures-cpupool have known vulnerabilities?

No known vulnerabilities on the latest version of futures-cpupool.

Is futures-cpupool deprecated?

No, futures-cpupool is actively maintained. Latest release: 0.1.8 (2018-01-02).

What are alternatives to futures-cpupool?

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

What license does futures-cpupool use?

futures-cpupool is licensed under MIT/Apache-2.0.

futures-cpupool

cargov0.1.8

An implementation of thread pools which hand out futures to the results of the computation on the threads themselves.

License MIT/Apache-2.0permissive9 versions0 deps464,806 weekly dl

alexcrichton/futures-rs

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

12/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/futures-cpupool