Is deep-merge safe to use?

deep-merge has no known vulnerabilities on the latest version (0.0.4). DepScope rates its health at 40/100 (high risk).

What is the latest version of deep-merge?

The latest version of deep-merge is 0.0.4, released 2018-03-27.

Does deep-merge have known vulnerabilities?

No known vulnerabilities on the latest version of deep-merge.

Is deep-merge deprecated?

No, deep-merge is actively maintained. Latest release: 0.0.4 (2018-03-27).

What are alternatives to deep-merge?

Popular alternatives to deep-merge in PyPI include: boto3, packaging, urllib3, idna, typing-extensions.

What license does deep-merge use?

deep-merge is licensed under MIT.

deep-merge

pypiv0.0.4

A simple utility for merging python dictionaries.

License MITpermissive4 versions1 maintainers0 deps27,654 weekly dl

halfak/deep_merge

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/deep-merge