fast-deep-equal

v3.1.3

Fast deep equal

MIT
Latest version published 2 years ago
    npm install fast-deep-equal
  

Package Health Score

70 / 100

Security

No known security issues
Powered by Snyk
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.1.3 | 06/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.1 | 11/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.1 | 04/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.0 | 02/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0 | 06/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test fast-deep-equal
Get started free

Popularity

Influential project

Weekly Downloads (37,423,231)

Download trend
Dependents
1.52K
GitHub Stars
1.5K
Forks
87
Contributors
20

Direct Usage Popularity

TOP 5%

The npm package fast-deep-equal receives a total of 37,423,231 downloads a week. As such, we scored fast-deep-equal popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package fast-deep-equal, we found that it has been starred 1,505 times, and that 1,524 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
Yes

With more than 10 contributors for the fast-deep-equal 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 fast-deep-equal is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 70/100 package health 70/100

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of fast-deep-equal 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 fast-deep-equal 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.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
not defined

Age
5 years
Dependencies
0 Direct
Versions
15
Install Size
13 kB
Dist-tags
2
# of Files
11
Maintainers
1
TS Typings
Yes

fast-deep-equal 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.