server-destroy

v1.0.1

Enable destroying a server, and all currently open connections.

ISC
Latest version published 7 years ago
    npm install server-destroy
  
We couldn't find any similar packages Browse all packages

Package Health Score

67 / 100

Popularity

Influential project

Weekly Downloads (1,324,809)

Download trend
Dependents
688
GitHub Stars
176
Forks
16
Contributors
1

Direct Usage Popularity

TOP 5%

The npm package server-destroy receives a total of 1,324,809 downloads a week. As such, we scored server-destroy popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package server-destroy, we found that it has been starred 176 times, and that 688 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
Popular

Version

Release Date

05/2015

Direct Vulnerabilities

Popular
1.0.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
1.0.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
1.0.1
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
ISC

Security Policy
No

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

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
3
Open PR
3
Last Release
7 years ago
Last Commit
7 years ago

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


Embed Package Health Score Badge

package health: 67/100 package health 67/100

Package

Node.js Compatibility
not defined

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

server-destroy 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.