npmpackage.info

Gathering detailed insights and metrics for server-destroy

server-destroy

When close() is just not enough

1.0.1

189

ISC

JavaScript

237.00 B

400,994,183 3

Installations

npm install server-destroy

Score

100

Supply Chain

66.6

Quality

74.9

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

3

Total

12

Closed

9

Issues

Open

3

Total

6

Closed

3

Releases

Unable to fetch releases

Developer

isaacs

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

2.0.1

NPM Version

2.10.0 Statistics

189 Stars

8 Commits

16 Forks

4 Watching

1 Branches

1 Contributors

Updated on 31 Aug 2024

Bundle Size

357.00 B

Minified

237.00 B

Minified + Gzipped

Bundlephobia

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

400,994,183

Last day

-4.2%

315,701

Compared to previous day

Last week

-1.3%

1,787,787

Compared to previous week

Last month

16%

7,783,885

Compared to previous month

Last year

8.6%

85,579,755

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

No dependencies detected.

Versions

server-destroy

Enable destroying a server, and all currently open connections.

Usage

1var enableDestroy = require('server-destroy');
2
3var server = http.createServer(function(req, res) {
4  // do stuff, blah blah blah
5});
6
7server.listen(PORT);
8
9// enhance with a 'destroy' function
10enableDestroy(server);
11
12// some time later...
13server.destroy();

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

SAST

Determines if the project uses static code analysis.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Security-Policy

Determines if the project has published a security policy.

Score

3

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More