Unitech/pm2

Prefer upstream PM2 for almost any new deployment. Choose this fork only if you specifically need its legacy customizations and are prepared to own the maintenance burden.

Prefer this fork only for legacy compatibility or if its fork-mode changes are exactly what you need. For new deployments, upstream PM2 is the better choice because this fork is extremely stale and likely missing major modern features and fixes.

Prefer upstream for almost all production use. This fork only makes sense if you specifically need its early legacy behavior or are inheriting an old codebase built around it.

Prefer this fork only if you specifically need its older customizations and are prepared to own maintenance. For most adopters, current upstream PM2 is the safer choice because this fork is stale and materially behind on features, compatibility, and fixes.

Prefer upstream unless you specifically need this fork's legacy/custom behavior. This fork looks significantly diverged and stale, so it is better suited to existing adopters than new users.

Prefer upstream unless you specifically need this fork’s no-vizion/no-autorestart-style behavior or its older customized workflow; the fork is too stale and too far behind for general adoption.

Choose this fork only if you need its older, customized behavior and are willing to own the maintenance burden. For new adoption, upstream PM2 is the safer choice because it is far newer, active, and materially more capable.

Prefer upstream PM2 unless you specifically need this fork's legacy cluster and process-state tweaks. This fork is too old and too far behind for most new production use.

Choose this fork if your main pain point is PM2 TypeScript typing quality; otherwise upstream is the safer default because this fork does not materially change runtime behavior or add new operational capabilities.