Is resque-lock-timeout safe to use?

resque-lock-timeout has no known vulnerabilities on the latest version (0.4.5). DepScope rates its health at 46/100 (high risk).

What is the latest version of resque-lock-timeout?

The latest version of resque-lock-timeout is 0.4.5, released 2015-08-04.

Does resque-lock-timeout have known vulnerabilities?

No known vulnerabilities on the latest version of resque-lock-timeout.

Is resque-lock-timeout deprecated?

No, resque-lock-timeout is actively maintained. Latest release: 0.4.5 (2015-08-04).

What are alternatives to resque-lock-timeout?

Popular alternatives to resque-lock-timeout in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does resque-lock-timeout use?

resque-lock-timeout is licensed under MIT.

resque-lock-timeout

rubygemsv0.4.5

A Resque plugin. Adds locking, with optional timeout/deadlock handling to resque jobs. Using a `lock_timeout` allows you to re-acquire the lock should your worker fail, crash, or is otherwise unable to relase the lock. i.e. Your server unexpectedly looses power. Very handy for jobs that are recurring or may be retried.

License MITpermissive9 versions1 deps748,887 weekly dl

http://github.com/lantins/resque-lock-timeout

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

6/15

maturity

1/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

resque

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/resque-lock-timeout