Is nearest_time_zone safe to use?

nearest_time_zone has no known vulnerabilities on the latest version (0.0.4). DepScope rates its health at 45/100 (high risk).

What is the latest version of nearest_time_zone?

The latest version of nearest_time_zone is 0.0.4, released 2015-02-19.

Does nearest_time_zone have known vulnerabilities?

No known vulnerabilities on the latest version of nearest_time_zone.

Is nearest_time_zone deprecated?

No, nearest_time_zone is actively maintained. Latest release: 0.0.4 (2015-02-19).

What are alternatives to nearest_time_zone?

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

What license does nearest_time_zone use?

nearest_time_zone is licensed under MIT.

nearest_time_zone

rubygemsv0.0.4

Quickly find the name of a time zone for a latitude and longitude without relying on a web service.

License MITpermissive4 versions3 deps1,332,121 weekly dl

/ 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

Dependencies (3)

andand kdtree require_all

API access

Get this data programmatically — free, no authentication.

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