autocomplete

v0.0.1

An in-memory autocomplete package based on the trie data structure

MIT
Latest version published 10 years ago
    npm install autocomplete
  

Package Health Score

45 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Limited

Weekly Downloads (290)

Download trend
Dependents
0
GitHub Stars
56
Forks
16
Contributors
4

Direct Usage Popularity

Uncommon

The npm package autocomplete receives a total of 290 downloads a week. As such, we scored autocomplete popularity level to be Limited.

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

08/2011

Direct Vulnerabilities

Popular
0.0.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
0.0.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
0.0.1
  • 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 autocomplete 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 autocomplete
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
4
Open PR
5
Last Release
10 years ago
Last Commit
6 years ago

Further analysis of the maintenance status of autocomplete 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 autocomplete 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
No
Contributing.md
No
Code of Conduct
No
Contributors
4
Funding
No

This project has seen only 10 or less contributors.

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

How about a good first contribution to this project? It seems that autocomplete is missing a README file.


Embed Package Health Score Badge

package health: 45/100 package health 45/100

Package

Node.js Compatibility
*

Age
10 years
Dependencies
0 Direct
Versions
2
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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