npmpackage.info

Gathering detailed insights and metrics for cluster-adapter-pm2

cluster-adapter-pm2 - 5.3.0 | npmpackage.info

cluster-adapter-pm2

Node.js Production Process Manager with a built-in Load Balancer.

5.3.0

42,396

NOASSERTION

JavaScript

772.26 kB

4.2

Installations

npm install cluster-adapter-pm2

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Min. Node Version

>=10.0.0

Node Version

18.12.0

NPM Version

8.19.2 Pull Requests

Open

63

Total

913

Closed

299

Merged

551

Issues

Open

995

Total

5,073

Closed

4,078

Releases

128

v6.0.8

Updated on Jun 05, 2025

v6.0.7

Updated on Jun 05, 2025

v6.0.6

Updated on May 13, 2025

v6.0.5

Updated on Mar 15, 2025

v5.4.2

Updated on Jul 08, 2024

5.4.1

v5.4.1

Updated on Jun 18, 2024

View All 128 releases

Languages

JavaScript

Shell

Smarty

Dockerfile

Python

PowerShell

JavaScript (81.29%)

Shell (18.06%)

Smarty (0.59%)

Dockerfile (0.03%)

Python (0.01%)

PowerShell (0.01%)

Developer

Unitech

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

NOASSERTION License

42,396 Stars

5,117 Commits

2,650 Forks

641 Watchers

12 Branches

283 Contributors

Updated on Jul 16, 2025

Maintainers

View All 283 Contributors

Package Meta Information

Latest Version

5.3.0

Package Id

cluster-adapter-pm2@5.3.0

Unpacked Size

772.26 kB

Size

208.33 kB

File Count

123

NPM Version

8.19.2

Node Version

18.12.0

Published on

Apr 18, 2023

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

Dev Dependencies

mocha should

Optional Dependencies

pm2-sysmonit

P(rocess) M(anager) 2
Runtime Edition

PM2 is a production process manager for Node.js applications with a built-in load balancer. It allows you to keep applications alive forever, to reload them without downtime and to facilitate common system admin tasks.

Starting an application in production mode is as easy as:

1$ pm2 start app.js

PM2 is constantly assailed by more than 1800 tests.

Official website: https://pm2.keymetrics.io/

Works on Linux (stable) & macOS (stable) & Windows (stable). All Node.js versions are supported starting Node.js 12.X.

Installing PM2

With NPM:

1$ npm install pm2 -g

You can install Node.js easily with NVM or ASDF.

Start an application

You can start any application (Node.js, Python, Ruby, binaries in $PATH...) like that:

1$ pm2 start app.js

Your app is now daemonized, monitored and kept alive forever.

Managing Applications

Once applications are started you can manage them easily:

Process listing

To list all running applications:

1$ pm2 list

Managing apps is straightforward:

1$ pm2 stop     <app_name|namespace|id|'all'|json_conf>
2$ pm2 restart  <app_name|namespace|id|'all'|json_conf>
3$ pm2 delete   <app_name|namespace|id|'all'|json_conf>

To have more details on a specific application:

1$ pm2 describe <id|app_name>

To monitor logs, custom metrics, application information:

1$ pm2 monit

More about Process Management

Cluster Mode: Node.js Load Balancing & Zero Downtime Reload

The Cluster mode is a special mode when starting a Node.js application, it starts multiple processes and load-balance HTTP/TCP/UDP queries between them. This increase overall performance (by a factor of x10 on 16 cores machines) and reliability (faster socket re-balancing in case of unhandled errors).

Framework supported

Starting a Node.js application in cluster mode that will leverage all CPUs available:

1$ pm2 start api.js -i <processes>

<processes> can be 'max', -1 (all cpu minus 1) or a specified number of instances to start.

Zero Downtime Reload

Hot Reload allows to update an application without any downtime:

1$ pm2 reload all

More informations about how PM2 make clustering easy

Container Support

With the drop-in replacement command for node, called pm2-runtime, run your Node.js application in a hardened production environment. Using it is seamless:

RUN npm install pm2 -g
CMD [ "pm2-runtime", "npm", "--", "start" ]

Host monitoring speedbar

PM2 allows to monitor your host/server vitals with a monitoring speedbar.

To enable host monitoring:

1$ pm2 set pm2:sysmonit true
2$ pm2 update

Framework supported

Terminal Based Monitoring

Monit

Monitor all processes launched straight from the command line:

1$ pm2 monit

Log Management

To consult logs just type the command:

1$ pm2 logs

Standard, Raw, JSON and formated output are available.

Examples:

1$ pm2 logs APP-NAME       # Display APP-NAME logs
2$ pm2 logs --json         # JSON output
3$ pm2 logs --format       # Formated output
4
5$ pm2 flush               # Flush all logs
6$ pm2 reloadLogs          # Reload all logs

To enable log rotation install the following module

1$ pm2 install pm2-logrotate

More about log management

Startup Scripts Generation

PM2 can generate and configure a Startup Script to keep PM2 and your processes alive at every server restart.

Init Systems Supported: systemd, upstart, launchd, rc.d

1# Generate Startup Script
2$ pm2 startup
3
4# Freeze your process list across server restart
5$ pm2 save
6
7# Remove Startup Script
8$ pm2 unstartup

More about Startup Scripts Generation

Updating PM2

1# Install latest PM2 version
2$ npm install pm2@latest -g
3# Save process list, exit old PM2 & restore all processes
4$ pm2 update

PM2 updates are seamless

PM2+ Monitoring

If you manage your apps with PM2, PM2+ makes it easy to monitor and manage apps across servers.

Feel free to try it:

Discover the monitoring dashboard for PM2

Thanks in advance and we hope that you like PM2!

CHANGELOG

Contributors

License

PM2 is made available under the terms of the GNU Affero General Public License 3.0 (AGPL 3.0). For other licenses contact us.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Maintained

Determines if the project is "actively maintained".

10

Binary-Artifacts

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

9

License

Determines if the project has defined a license.

9

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Code-Review

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

0

CII-Best-Practices

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

0

Security-Policy

Determines if the project has published a security policy.

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

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 0

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/Unitech/pm2/node.js.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/node.js.yml:50: update your workflow using https://app.stepsecurity.io/secureworkflow/Unitech/pm2/node.js.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/Unitech/pm2/node.js.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/Unitech/pm2/node.js.yml/master?enable=pin
Warn: containerImage not pinned by hash: examples/docker-pm2/Dockerfile:1: pin your Docker image by updating keymetrics/pm2:latest-alpine to keymetrics/pm2:latest-alpine@sha256:6af98b5fffecfac2ca565d3df189980fbc83e18d07359bd81e518f49687f842c
Warn: containerImage not pinned by hash: test/Dockerfile:1: pin your Docker image by updating node:alpine to node:alpine@sha256:22b3c1a1171c798c0429f36272922dbb356bbab8a6d11b3b095a143d3321262a
Warn: containerImage not pinned by hash: test/fixtures/containerizer/Dockerfile.dev:1: pin your Docker image by updating mhart/alpine-node:latest to mhart/alpine-node:latest@sha256:c9014e9e5b33f29d47c867ea548edc0235ba71677f40456409a44c278d8a8e01
Warn: containerImage not pinned by hash: test/fixtures/containerizer/Dockerfile.prod:1: pin your Docker image by updating mhart/alpine-node:latest to mhart/alpine-node:latest@sha256:c9014e9e5b33f29d47c867ea548edc0235ba71677f40456409a44c278d8a8e01
Warn: containerImage not pinned by hash: test/fixtures/docker/expressor/Dockerfile.bak:1: pin your Docker image by updating keymetrics/pm2:latest to keymetrics/pm2:latest@sha256:ebc9a08b9f6181ac876ac9153523911eac163177cb2e379950282118af4273c0
Warn: npmCommand not pinned by hash: examples/docker-pm2/Dockerfile:9
Warn: npmCommand not pinned by hash: lib/templates/Dockerfiles/Dockerfile-java.tpl:4
Warn: npmCommand not pinned by hash: lib/templates/Dockerfiles/Dockerfile-nodejs.tpl:8
Warn: npmCommand not pinned by hash: lib/templates/Dockerfiles/Dockerfile-ruby.tpl:4
Warn: npmCommand not pinned by hash: test/Dockerfile:12
Warn: npmCommand not pinned by hash: test/fixtures/containerizer/Dockerfile.dev:4
Warn: npmCommand not pinned by hash: test/fixtures/containerizer/Dockerfile.dev:10
Warn: npmCommand not pinned by hash: test/fixtures/containerizer/Dockerfile.prod:4
Warn: npmCommand not pinned by hash: test/fixtures/containerizer/Dockerfile.prod:10
Warn: npmCommand not pinned by hash: test/fixtures/docker/expressor/Dockerfile.bak:8
Warn: npmCommand not pinned by hash: packager/build-dist.sh:14
Warn: downloadThenRun not pinned by hash: packager/setup.deb.sh:129
Warn: downloadThenRun not pinned by hash: packager/setup.rpm.sh:148
Warn: npmCommand not pinned by hash: .github/workflows/node.js.yml:28
Info: 0 out of 3 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 1 third-party GitHubAction dependencies pinned
Info: 0 out of 5 containerImage dependencies pinned
Info: 0 out of 12 npmCommand dependencies pinned
Info: 0 out of 2 downloadThenRun dependencies pinned

0

SAST

Determines if the project uses static code analysis.

Score

4.2

/10

Last Scanned on 2025-07-14

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