limiter

v1.1.5

A generic rate limiter for node.js. Useful for API clients, web crawling, or other tasks that need to be throttled

MIT
Latest version published 1 year ago
    npm install limiter
  

Package Health Score

71 / 100
Make sure the open source you're using is safe to use
Secure my Project

Popularity

Influential project

Weekly Downloads (1,323,161)

Dependents
237
GitHub Stars
1.14K
Forks
105
Contributors
20

The npm package limiter receives a total of 1,323,161 downloads a week. As such, we scored limiter popularity level to be Influential project.

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

Direct Vulnerabilities

0.0.2
1.0.5
1.1.5
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.2
1.0.5
1.1.5
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.2
1.0.5
1.1.5
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 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 limiter 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 && snyk test limiter
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
10
Merged PR
19
Open PR
2
Last Commit
1 month ago

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

Community

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

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


Embed Package Health Score Badge

package health: 71/100 package health 71/100

Package

Node.js Compatibility
not defined

Age
9 years
Dependencies
0 Direct
Versions
14
Install Size
23.2 kB
Dist-tags
1
# of Files
12
Maintainers
1
TS Typings
Yes

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