Is debug_panic safe to use?

debug_panic has no known vulnerabilities on the latest version (0.2.1). DepScope rates its health at 51/100 (high risk).

What is the latest version of debug_panic?

The latest version of debug_panic is 0.2.1, released 2020-02-10.

Does debug_panic have known vulnerabilities?

No known vulnerabilities on the latest version of debug_panic.

Is debug_panic deprecated?

No, debug_panic is actively maintained. Latest release: 0.2.1 (2020-02-10).

What are alternatives to debug_panic?

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

What license does debug_panic use?

debug_panic is licensed under MIT.

debug_panic

cargov0.2.1

This allows a program to terminate immediately and provide feedback to the caller of the program. Unlike panic!, debug_panic! statements are only enabled in non optimized builds by default.

License MITpermissive4 versions0 deps106,451 weekly dl

kellytk/debug_panic

/ 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/debug_panic