Is resque-lock safe to use?

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

What is the latest version of resque-lock?

The latest version of resque-lock is 1.1.0, released 2012-11-08.

Does resque-lock have known vulnerabilities?

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

Is resque-lock deprecated?

No, resque-lock is actively maintained. Latest release: 1.1.0 (2012-11-08).

What are alternatives to resque-lock?

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

What license does resque-lock use?

License information for resque-lock is not declared in the registry metadata.

resque-lock

rubygemsv1.1.0

A Resque plugin. If you want only one instance of your job queued at a time, extend it with this module. For example: class UpdateNetworkGraph extend Resque::Jobs::Locked def self.perform(repo_id) heavy_lifting end end

4 versions0 deps1,240,384 weekly dl

http://github.com/defunkt/resque-lock

/ 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/resque-lock