Is deep_merge_existing_keys safe to use?

deep_merge_existing_keys has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 34/100 (critical risk).

What is the latest version of deep_merge_existing_keys?

The latest version of deep_merge_existing_keys is 1.1.0, released 2020-04-27.

Does deep_merge_existing_keys have known vulnerabilities?

No known vulnerabilities on the latest version of deep_merge_existing_keys.

Is deep_merge_existing_keys deprecated?

No, deep_merge_existing_keys is actively maintained. Latest release: 1.1.0 (2020-04-27).

What are alternatives to deep_merge_existing_keys?

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

What license does deep_merge_existing_keys use?

deep_merge_existing_keys is licensed under MIT.

deep_merge_existing_keys

rubygemsv1.1.0

Extends Rails's deep_merge method to merge only existing keys.

License MITpermissive3 versions1 deps2,918 weekly dl

lespoupeesrusses/deep_merge_existing_keys

/ 100

Health

use with caution

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

Low health score (34/100)

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

rails

API access

Get this data programmatically — free, no authentication.

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