alert

connect-timeout

v1.9.0

Request timeout middleware for Connect/Express

MIT
Latest version published 4 years ago
    npm install connect-timeout
  

Explore Similar Packages

Package Health Score

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

Popularity

Popular
Download trend

Weekly Downloads (184,684)

Dependents
192
GitHub Stars
288
Forks
44
Contributors
8

The npm package connect-timeout receives a total of 184,684 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 288 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.

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.0.1
1.8.0
1.9.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.1
1.8.0
1.9.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.1
1.8.0
1.9.0
  • 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 connect-timeout 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 connect-timeout
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
1
Open PR
2
Last Release
4 years ago
Last Commit
4 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.

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

Package

Node.js Compatibility
>= 0.8

Age
10 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.