Is time_for_a_boolean safe to use?

time_for_a_boolean has no known vulnerabilities on the latest version (0.3.0). DepScope rates its health at 59/100 (high risk).

What is the latest version of time_for_a_boolean?

The latest version of time_for_a_boolean is 0.3.0, released 2026-01-13.

No known vulnerabilities on the latest version of time_for_a_boolean.

No, time_for_a_boolean is actively maintained. Latest release: 0.3.0 (2026-01-13).

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

time_for_a_boolean is licensed under MIT.

rubygemsv0.3.0

Use timestamp values to represent boolean data such as deleted, published, or subscribed.

License MITpermissive11 versions2 deps14,312 weekly dl

59

/ 100

Health

safe to use

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

Health breakdown0 – 100

15/25

maintenance

10/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

0

none known

Dependencies (2)

API access

Get this data programmatically — free, no authentication.

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