Is concurrent-ruby-edge safe to use?

concurrent-ruby-edge has no known vulnerabilities on the latest version (0.7.2). DepScope rates its health at 53/100 (high risk).

What is the latest version of concurrent-ruby-edge?

The latest version of concurrent-ruby-edge is 0.7.2, released 2025-01-15.

Does concurrent-ruby-edge have known vulnerabilities?

No known vulnerabilities on the latest version of concurrent-ruby-edge.

Is concurrent-ruby-edge deprecated?

No, concurrent-ruby-edge is actively maintained. Latest release: 0.7.2 (2025-01-15).

What are alternatives to concurrent-ruby-edge?

Popular alternatives to concurrent-ruby-edge in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does concurrent-ruby-edge use?

concurrent-ruby-edge is licensed under MIT.

concurrent-ruby-edge

rubygemsv0.7.2

These features are under active development and may change frequently. They are expected not to keep backward compatibility (there may also lack tests and documentation). Semantic versions will be obeyed though. Features developed in `concurrent-ruby-edge` are expected to move to `concurrent-ruby` when final. Please see http://concurrent-ruby.com for more information.

License MITpermissive20 versions1 deps771,851 weekly dl

http://www.concurrent-ruby.com

/ 100

Health

safe to use

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

Health breakdown0 – 100

5/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

concurrent-ruby

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/concurrent-ruby-edge