Package Health Score

36 / 100

security
Security review needed
popularity
Limited
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
0.1.0	\|	08/2013	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

Unknown

Unable to detect license

We couldn’t find an appropriate license for this project. It is highly advised to make sure the project license is compatible with your business needs before including it as a dependency, to keep yourself protected from infringement suits or loss of your own code.

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

Limited

Weekly Downloads (54)

GitHub Stars: 5
Forks: 1
Contributors: -

Direct Usage Popularity

The npm package killer receives a total of 54 downloads a week. As such, we scored killer popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package killer, we found that it has been starred 5 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: No
Contributors: 0
Funding: No

This project has seen only 10 or less contributors.

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

How about a good first contribution to this project? It seems that killer is missing a LICENSE file.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 0
Open PR: 1
Last Release: 11 years ago
Last Commit: 11 years ago

Further analysis of the maintenance status of killer 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 killer 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.

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: not defined

Age: 11 years
Dependencies: 0 Direct
Versions: 2
Install Size: 0 B
Dist-tags: 1
# of Files: 0
Maintainers: 1
TS Typings: No

killer 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

killer

It makes sure that your processes are dead.

Usage

Example

The following example uses killer to kill a child process after an hour.

var spawn = require('child_process').spawn,
    killer = require('killer');

var child = spawn('node', ['server.js']);
setTimeout(function () {
  // Ensure that the server is dead.
  killer(child.pid, function () {
    console.log('Child process killed');
  });
}, 60 * 60 * 1000);

`killer(options, callback)`

`options`

If options is a string or a number, it's assumed to be the PID. Defaults are used for all other options.

pid - PID of the process to kill
interval - How often to check if process is still alive (default: 1000). Setting to false disables polling.
killSignal - which signal to use to kill the process (default: SIGKILL)
termSignal - which signal to use to terminate the process after timeout (default: SIGTERM)
timeout - when to send termSignal to the process (default: 10000).

`callback`

Called when process is dead.

killer development dependencies

assert-called

FAQs

What is killer?

It makes sure that your processes are dead. Visit Snyk Advisor to see a full health score report for killer, including popularity, security, maintenance & community analysis.

Is killer popular?

The npm package killer receives a total of 54 weekly downloads. As such, killer popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is killer well maintained?

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

Is killer safe to use?

While scanning the latest version of killer, 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 20 November-2024, at 03:21 (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

killer

It makes sure that your processes are dead. 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

Unable to detect license

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (54)

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

killer

Usage

Example

`killer(options, callback)`

`options`

`callback`

killer development dependencies

FAQs

What is killer?

Is killer popular?

Is killer well maintained?

Is killer 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 (54)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

killer

Usage

Example

killer(options, callback)

options

callback

killer development dependencies

FAQs

What is killer?

Is killer popular?

Is killer well maintained?

Is killer 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

`killer(options, callback)`

`options`

`callback`