connect

v3.7.0

High performance middleware framework

MIT
Latest version published 2 years ago
    npm install connect
  

Package Health Score

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

Popularity

Key ecosystem project

Weekly Downloads (4,442,731)

Dependents
4.86K
GitHub Stars
9.08K
Forks
1.13K
Contributors
130

The npm package connect receives a total of 4,442,731 downloads a week. As such, we scored connect popularity level to be Key ecosystem project.

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

1.8.7
1.9.2
2.30.2
3.6.6
3.7.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.8.7
1.9.2
2.30.2
3.6.6
3.7.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

1.8.7
1.9.2
2.30.2
3.6.6
3.7.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 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
Yes

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

Maintenance

Sustainable

Commit Frequency

Open Issues
1
Open PR
1
Last Release
2 years ago
Last Commit
7 months ago

Further analysis of the maintenance status of connect based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

An important project maintenance signal to consider for connect 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

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

A good and healthy external contribution signal for connect project, which invites more than one hundred open source maintainers to collaborate on the repository.

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


Embed Package Health Score Badge

package health: 77/100 package health 77/100

Package

Node.js Compatibility
>= 0.10.0

Age
10 years
Dependencies
4 Direct
Versions
237
Install Size
95.2 kB
Dist-tags
2
# of Files
6
Maintainers
2
TS Typings
Yes

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