Is maybe-async-cfg safe to use?

maybe-async-cfg has no known vulnerabilities on the latest version (0.2.5). DepScope rates its health at 49/100 (high risk).

What is the latest version of maybe-async-cfg?

The latest version of maybe-async-cfg is 0.2.5, released 2024-11-03.

Does maybe-async-cfg have known vulnerabilities?

No known vulnerabilities on the latest version of maybe-async-cfg.

Is maybe-async-cfg deprecated?

No, maybe-async-cfg is actively maintained. Latest release: 0.2.5 (2024-11-03).

What are alternatives to maybe-async-cfg?

Popular alternatives to maybe-async-cfg in Cargo include: hashbrown, getrandom, windows-sys, syn.

What license does maybe-async-cfg use?

maybe-async-cfg is licensed under MIT.

maybe-async-cfg

cargov0.2.5

A procedure macro to unify sync and async implementations depending on the features of your crate

License MITpermissive8 versions0 deps55,646 weekly dl

nvksv/maybe-async-cfg

/ 100

Health

safe to use

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

Health breakdown0 – 100

5/25

maintenance

10/20

popularity

25/25

security

9/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/maybe-async-cfg