fuzzy

v0.1.3

small, standalone fuzzy search / fuzzy filter. browser or node

MIT
Latest version published 5 years ago
    npm install fuzzy
  

Package Health Score

53 / 100

Popularity

Popular

Weekly Downloads (317,092)

Download trend
Dependents
739
GitHub Stars
763
Forks
82
Contributors
8

Direct Usage Popularity

TOP 5%

The npm package fuzzy receives a total of 317,092 downloads a week. As such, we scored fuzzy popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package fuzzy, we found that it has been starred 763 times, and that 739 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.

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

10/2016

Direct Vulnerabilities

Popular
0.1.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
0.1.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
0.1.3
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like fuzzy is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test fuzzy
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
19
Open PR
8
Last Release
5 years ago
Last Commit
5 years ago

Further analysis of the maintenance status of fuzzy 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 fuzzy 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.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
8
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 53/100 package health 53/100

Package

Node.js Compatibility
>= 0.6.0

Age
9 years
Dependencies
0 Direct
Versions
5
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
Yes

fuzzy 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.