Is retry-after safe to use?

retry-after has no known vulnerabilities on the latest version (0.4.0). DepScope rates its health at 50/100 (high risk).

What is the latest version of retry-after?

The latest version of retry-after is 0.4.0, released 2024-03-14.

Does retry-after have known vulnerabilities?

No known vulnerabilities on the latest version of retry-after.

Is retry-after deprecated?

No, retry-after is actively maintained. Latest release: 0.4.0 (2024-03-14).

What are alternatives to retry-after?

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

What license does retry-after use?

retry-after is licensed under MIT OR Apache-2.0.

retry-after

cargov0.4.0

Retry-After header for Hyper's header module

License MIT OR Apache-2.0permissive5 versions0 deps13,344 weekly dl

jwilm/retry-after

/ 100

Health

use with caution

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

Moderate health score (50/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

15/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/retry-after