Is mutually_exclusive_features safe to use?

mutually_exclusive_features has no known vulnerabilities on the latest version (0.1.0). DepScope rates its health at 48/100 (high risk).

What is the latest version of mutually_exclusive_features?

The latest version of mutually_exclusive_features is 0.1.0, released 2024-02-05.

Does mutually_exclusive_features have known vulnerabilities?

No known vulnerabilities on the latest version of mutually_exclusive_features.

Is mutually_exclusive_features deprecated?

No, mutually_exclusive_features is actively maintained. Latest release: 0.1.0 (2024-02-05).

What are alternatives to mutually_exclusive_features?

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

What license does mutually_exclusive_features use?

mutually_exclusive_features is licensed under MIT OR Apache-2.0.

mutually_exclusive_features

cargov0.1.0

Macros to check that only none or one of a set of features is enabled at a time, as known as mutually exclusive features

License MIT OR Apache-2.0permissive4 versions0 deps1,190,809 weekly dl

omid/mutually_exclusive_features

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

6/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/mutually_exclusive_features