Is key_path safe to use?

key_path has no known vulnerabilities on the latest version (1.2.0). DepScope rates its health at 38/100 (critical risk).

What is the latest version of key_path?

The latest version of key_path is 1.2.0, released 2016-04-12.

Does key_path have known vulnerabilities?

No known vulnerabilities on the latest version of key_path.

Is key_path deprecated?

No, key_path is actively maintained. Latest release: 1.2.0 (2016-04-12).

What are alternatives to key_path?

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

What license does key_path use?

key_path is licensed under MIT.

key_path

rubygemsv1.2.0

Keypath-based collection access extensions for Ruby.

License MITpermissive4 versions1 deps71,274 weekly dl

nickcharlton/keypath-ruby

/ 100

Health

use with caution

[email protected] low health (38/100) — consider alternatives

Low health score (38/100)

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

activesupport

API access

Get this data programmatically — free, no authentication.

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