Is serde-rename-rule safe to use?

serde-rename-rule has no known vulnerabilities on the latest version (0.2.3). DepScope rates its health at 63/100 (moderate risk).

What is the latest version of serde-rename-rule?

The latest version of serde-rename-rule is 0.2.3, released 2026-01-03.

Does serde-rename-rule have known vulnerabilities?

No known vulnerabilities on the latest version of serde-rename-rule.

Is serde-rename-rule deprecated?

No, serde-rename-rule is actively maintained. Latest release: 0.2.3 (2026-01-03).

What are alternatives to serde-rename-rule?

Popular alternatives to serde-rename-rule in Cargo include: hashbrown, getrandom, windows-sys, syn.

What license does serde-rename-rule use?

serde-rename-rule is licensed under Apache-2.0 OR MIT.

serde-rename-rule

cargov0.2.3

Serde RenameRule

License Apache-2.0 OR MITpermissive7 versions0 deps938,440 weekly dl

bk-rs/serde-ext

/ 100

Health

use with caution

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

Moderate health score (63/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

14/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/serde-rename-rule