alert

send

v0.17.1

Better streaming static file server with Range and conditional-GET support

MIT
Latest version published 2 years ago
    npm install send
  

Package Health Score

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

Popularity

Influential project
Download trend

Weekly Downloads (18,892,761)

Dependents
1.15K
GitHub Stars
704
Forks
179
Contributors
30

The npm package send receives a total of 18,892,761 downloads a week. As such, we scored send popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package send, we found that it has been starred 704 times, and that 1,148 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.13.2
0.14.2
0.15.6
0.16.2
0.17.1
  • 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

Indirect Vulnerabilities

0.13.2
0.14.2
0.15.6
0.16.2
0.17.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.13.2
0.14.2
0.15.6
0.16.2
0.17.1
  • 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
No

We found a way for you to contribute to the project! Looks like send 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 send
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

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

Further analysis of the maintenance status of send 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 send 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
30
Funding
No

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


Embed Package Health Score Badge

package health: 70/100 package health 70/100

Package

Node.js Compatibility
>= 0.8.0

Age
9 years
Dependencies
13 Direct
Versions
59
Install Size
48.2 kB
Dist-tags
1
# of Files
5
Maintainers
1
TS Typings
Yes

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