Is thread_safe safe to use?

thread_safe has no known vulnerabilities on the latest version (0.3.6). DepScope rates its health at 54/100 (high risk).

What is the latest version of thread_safe?

The latest version of thread_safe is 0.3.6, released 2017-02-22.

Does thread_safe have known vulnerabilities?

No known vulnerabilities on the latest version of thread_safe.

Is thread_safe deprecated?

No, thread_safe is actively maintained. Latest release: 0.3.6 (2017-02-22).

What are alternatives to thread_safe?

Popular alternatives to thread_safe in RubyGems include: jmespath, netrc, crass, tzinfo, websocket-extensions.

What license does thread_safe use?

thread_safe is licensed under Apache-2.0.

thread_safe

rubygemsv0.3.6

A collection of data structures and utilities to make thread-safe programming in Ruby easier

License Apache-2.0permissive20 versions0 deps479,819,484 weekly dl

ruby-concurrency/thread_safe

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

20/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

OSS Scorecard

OpenSSF security posture score

2.3/10

poor

Maintainer trust

Active maintainers (3m)

1

Contributors (12m)

0

Primary author dominance

0%

GitHub stars

192

single active maintainer 3marchived repo

Quality signals

OSS Criticality

0.53high

Download trend

stable(0%)

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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