connect-pause

v0.1.0

Connect/Express middleware to simulate latency for debugging

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

Package Health Score

50 / 100

Popularity

Popular

Weekly Downloads (134,032)

Download trend
Dependents
51
GitHub Stars
12
Forks
2
Contributors
1

Direct Usage Popularity

TOP 10%

The npm package connect-pause receives a total of 134,032 downloads a week. As such, we scored connect-pause popularity level to be Popular.

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

Version

Release Date

05/2013

Direct Vulnerabilities

0.1.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.1.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

0.1.0
  • 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-pause 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-pause
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
0
Last Release
9 years ago
Last Commit
9 years ago

Further analysis of the maintenance status of connect-pause 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-pause 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
1
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-pause is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 50/100 package health 50/100

Package

Node.js Compatibility
*

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

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