Package Health Score

55 / 100

security
Security review needed
popularity
Recognized
maintenance
Inactive
community
Limited

Explore Similar Packages

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
3.2.1	\|	11/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.1.0	\|	07/2022	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.3.0	\|	04/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.1.0	\|	07/2019		0 C 0 H 1 M 0 L	0 H 0 M 0 L
1.0.1	\|	07/2019		0 C 0 H 1 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Recognized

Weekly Downloads (79,282)

GitHub Stars: 28
Forks: 3
Contributors: -

Direct Usage Popularity

The npm package kill-port-process receives a total of 79,282 downloads a week. As such, we scored kill-port-process popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package kill-port-process, we found that it has been starred 28 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: Yes
Contributing.md: No
Code of Conduct: Yes
Contributors: 0
Funding: No

This project has seen only 10 or less contributors.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 2
Open PR: 2
Last Release: 1 year ago
Last Commit: 1 month ago

Further analysis of the maintenance status of kill-port-process 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 kill-port-process 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=14

Age: 6 years
Dependencies: 2 Direct
Versions: 21
Install Size: 23.4 kB
Dist-tags: 2
# of Files: 21
Maintainers: 1
TS Typings: Yes

kill-port-process 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.

Readme

Kill-port-process

Cross-platform module to stop one (or more) process(es) running on a port (or a list of ports).

Install

$ npm install kill-port-process
# or
$ yarn add kill-port-process

Usage

Programmatically

const { killPortProcess&nbsp;} = require('kill-port-process');

(async () =&gt; {
  // long running process running on a given port(s), e.g. a http-server
  // takes a number, number[], string or string[]
  // single port
  await killPortProcess(1234);

  // multiple ports
  await killPortProcess([1234, 6789]);

  // with options
  await killPortProcess(1234, { signal: 'SIGTERM' });
})();

Options

signal (optional): used to determine the command used to kill the provided port(s). Valid values are:
- SIGKILL (default)
- SIGTERM

CLI

Install the module globally:

npm install kill-port-process -g

You can use the CLI calling it with kill-port .

It takes a single port or a list of ports separated by a space. Valid flags are -p and --port but are both optional.

$ kill-port 1234
# or multiple ports, separated by space(s)
$ kill-port 1234 2345
# or
$ kill-port -p 1234
# or
$ kill-port --port 1234

Flags

--graceful kill the process gracefully.
- Unix: Sends a -15 signal to kill (SIGTERM) rather than -9 (SIGKILL)
- Win: Currently no use

kill-port-process dependencies

get-them-args pid-from-port

kill-port-process development dependencies

@types/chai @types/mocha @types/node @types/node-fetch @types/pid-from-port @typescript-eslint/eslint-plugin @typescript-eslint/parser chai eslint mocha node-fetch ts-node typescript

FAQs

What is kill-port-process?

Easily kill hanging processes on ports - on any platform!. Visit Snyk Advisor to see a full health score report for kill-port-process, including popularity, security, maintenance & community analysis.

Is kill-port-process popular?

The npm package kill-port-process receives a total of 79,282 weekly downloads. As such, kill-port-process popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is kill-port-process well maintained?

We found indications that kill-port-process is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is kill-port-process safe to use?

While scanning the latest version of kill-port-process, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 29 November-2024, at 06:42 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

kill-port-process

Easily kill hanging processes on ports - on any platform! For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (79,282)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Readme

Kill-port-process

Install

Usage

Programmatically

Options

CLI

Flags

kill-port-process dependencies

kill-port-process development dependencies

FAQs

What is kill-port-process?

Is kill-port-process popular?

Is kill-port-process well maintained?

Is kill-port-process safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (79,282)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

Kill-port-process

Install

Usage

Programmatically

Options

CLI

Flags

kill-port-process dependencies

kill-port-process development dependencies

FAQs

What is kill-port-process?

Is kill-port-process popular?

Is kill-port-process well maintained?

Is kill-port-process safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues