Is deep-rename-keys safe to use?

deep-rename-keys has no known vulnerabilities on the latest version (0.2.1). DepScope rates its health at 57/100 (high risk).

What is the latest version of deep-rename-keys?

The latest version of deep-rename-keys is 0.2.1, released 2017-04-03.

Does deep-rename-keys have known vulnerabilities?

No known vulnerabilities on the latest version of deep-rename-keys.

Is deep-rename-keys deprecated?

No, deep-rename-keys is actively maintained. Latest release: 0.2.1 (2017-04-03).

What are alternatives to deep-rename-keys?

Popular alternatives to deep-rename-keys in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does deep-rename-keys use?

deep-rename-keys is licensed under MIT.

deep-rename-keys

npmv0.2.1

Recursively rename the keys in an object.

License MITpermissive3 versions2 maintainers2 deps235,353 weekly dl

jonschlinkert/deep-rename-keys

/ 100

Health

use with caution

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

Moderate health score (57/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

15/15

maturity

3/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

kind-of rename-keys

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/deep-rename-keys