connect-timeout

v1.9.0

Request timeout middleware for Connect/Express

MIT
Latest version published 5 years ago
    npm install connect-timeout
  
We couldn't find any similar packages Browse all packages

Package Health Score

56 / 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
1.9.0 | 05/2017
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.8.0 | 11/2016
  • 0
    H
  • 0
    M
  • 0
    L
0.0.1 | 02/2011
  • 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 connect-timeout
Get started free

Popularity

Popular

Weekly Downloads (185,563)

Download trend
Dependents
192
GitHub Stars
300
Forks
48
Contributors
8

Direct Usage Popularity

TOP 5%

The npm package connect-timeout receives a total of 185,563 downloads a week. As such, we scored connect-timeout popularity level to be Popular.

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

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 connect-timeout is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 56/100 package health 56/100

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of connect-timeout 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 connect-timeout 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
>= 0.8

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

connect-timeout 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.