Is deadlock_retry safe to use?

deadlock_retry has no known vulnerabilities on the latest version (1.2.0). DepScope rates its health at 45/100 (high risk).

What is the latest version of deadlock_retry?

The latest version of deadlock_retry is 1.2.0, released 2012-02-15.

Does deadlock_retry have known vulnerabilities?

No known vulnerabilities on the latest version of deadlock_retry.

Is deadlock_retry deprecated?

No, deadlock_retry is actively maintained. Latest release: 1.2.0 (2012-02-15).

What are alternatives to deadlock_retry?

Popular alternatives to deadlock_retry in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does deadlock_retry use?

License information for deadlock_retry is not declared in the registry metadata.

deadlock_retry

rubygemsv1.2.0

Provides automatic deadlock retry and logging functionality for ActiveRecord and MySQL

4 versions0 deps1,096,582 weekly dl

http://github.com/mperham/deadlock_retry

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

3/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/rubygems/deadlock_retry