Is master_lock safe to use?

master_lock has no known vulnerabilities on the latest version (0.11.1). DepScope rates its health at 46/100 (high risk).

What is the latest version of master_lock?

The latest version of master_lock is 0.11.1, released 2020-04-15.

Does master_lock have known vulnerabilities?

No known vulnerabilities on the latest version of master_lock.

Is master_lock deprecated?

No, master_lock is actively maintained. Latest release: 0.11.1 (2020-04-15).

What are alternatives to master_lock?

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

What license does master_lock use?

master_lock is licensed under Apache-2.0.

master_lock

rubygemsv0.11.1

This library implements application mutexes using Redis. The mutexes are shared between separate threads, processes, or machines. Locks are acquired with an expiration time so if process that holds a lock dies unexpectedly, the lock is released automatically after a certain duration.

License Apache-2.0permissive7 versions1 deps129,119 weekly dl

coinbase/master_lock

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

redis

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/master_lock