clean-deep

v3.4.0

Remove falsy, empty or nullable values from objects For more information about how to use this package see README

Latest version published 2 years ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

62 / 100

Explore Similar Packages

Security

No known security issues
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
3.4.0 | 08/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.3.0 | 02/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.2 | 03/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0 | 09/2016
  • 0
    H
  • 0
    M
  • 0
    L
0.0.1 | 11/2015
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Popular

Weekly Downloads (145,224)

Download trend
Dependents
106
GitHub Stars
144
Forks
25
Contributors
20

Direct Usage Popularity

TOP 10%

The npm package clean-deep receives a total of 145,224 downloads a week. As such, we scored clean-deep popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package clean-deep, we found that it has been starred 144 times, and that 106 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No

With more than 10 contributors for the clean-deep repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like clean-deep is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 62/100 package health 62/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
3
Open PR
15
Last Release
2 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of clean-deep based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for clean-deep is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=4

Age
7 years
Dependencies
3 Direct
Versions
16
Install Size
15.9 kB
Dist-tags
1
# of Files
9
Maintainers
3
TS Typings
No

clean-deep has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.