Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-12 19:44 UTC

Unitech / pm2

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

JavaScript · ShellCustom license★ 43,264 stars⑂ 2,719 forkssince May 2013View on GitHub ↗
KindCommand-line toolLibraryNetwork servicehow this is determined

Unitech/pm2 holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (93/100) and lowest on AI Readiness (46/100). It was last updated 41 days ago. A single contributor accounts for most of its recent work.

81
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

81
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 69 is calibrated to 81 on the published index scale (record calibration 2026-08-02).

Ownership

Alexandre StrzelewiczPersonal account
1,409 followers196 public repossince Apr 2011@keymetrics

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

75Good · 21% of overall
How it's scored
18/36Push recencylast push 41 days ago
12.5/36Commit cadence18/52 weeks with commits
18/18Commit volume110 commits in the last year
10/10OpenSSF Scorecard: Maintained13 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year110
human_commit_share1
days_since_last_push41
active_weeks_last_year18

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 44 days ago
27/27Release cadencea release every ~33.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv7.0.3
releases_from_tagsno
days_since_latest_release44
mean_days_between_releases33.4
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

93Exceptional · 17% of overall

Popularity & adoption

100Exceptional
How it's scored
60/60Stars43,264 stars
25/25Forks2,719 forks
15/15Watchers628 watchers
Inputs used
forks2,719
stars43,264
watchers628
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesbadge.fury.io, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads13,670,041 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespm2
dependents
ecosystemsnpm
total_downloads
monthly_downloads13,670,041
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.1/22.5Commit distributiontop contributor authored 68% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 83 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled100
top_contributor_share0.685
How it's scored
33.7/42Issue resolution80% of issues closed
18.9/30PR acceptance558/885 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs558
open_issues1,019
closed_issues4,127
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.802
closed_unmerged_prs327
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
22.6/25Owner reach1,409 followers of Unitech
25/25Track record196 public repos, account ~15 yr old
Inputs used
followers1,409
owner_typeUser
is_verified
owner_loginUnitech
public_repos196
account_age_days5,584
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 44 days ago
20/20Version history294 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespm2
ecosystemsnpm
any_deprecatedno
min_days_since_publish44

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://pm2.keymetrics.io/docs/usage/quick-start/
10/10Repository description
10/10Topics10 topics
0/10Wiki
Inputs used
topicspm2, nodejs, node, process-manager, monitoring, load-balancer, production, deploy, command-line, command-line-tool
has_wikino
homepagehttps://pm2.keymetrics.io/docs/usage/quick-start/
docs_sitehttps://pm2.keymetrics.io/docs/usage/quick-start/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

49Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 83 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained13 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories1 affected: js-yaml 4.3.0 (high 7.5)
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
40/40No advisories left outstandingno advisory has been public longer than 90 days
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages77
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Matched the npm:pm2@7.0.3 runtime dependency closure — what installing the published package pulls in — 77 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
6.9/40Legible commit history13 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.13
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapmodules/pm2-axon/lib/configurable/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtypes/tsconfig.json
10/10Reproducible environmentDockerfile
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_filesmodules/pm2-axon/lib/configurable/Makefile
has_devcontainerno
has_linter_configno
typecheck_configstypes/tsconfig.json
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codeJavaScript with type-check config (types/tsconfig.json)
54.8/55Manageable file sizes2/597 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes110,836
source_files_sampled597
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

43,264GitHub stars
100contributors
110commits, last 12 months
41days since last push
100releases
1bus factor
1,019open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 2,719 ⇿
0Stars
2,719Forks
49Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

1,5001,7502,0002,2502,5002,7502,71992019-062023-012026-08
Major 3Minor 8Patch 34

Each point covers 7 days.

OpenSSF Scorecard 4.1 / 10
4.1aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-12 19:44 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 83 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained13 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 22
RegistryPackageVersion constraintManifest
npm@pm2/blessed0.1.81package.json
npm@pm2/js-api0.8.1package.json
npm@pm2/pm2-version-check1.0.4package.json
npmamp0.3.1package.json
npmamp-message0.1.2package.json
npmansis4.0.0-node10package.json
npmasync3.2.6package.json
npmchokidar3.6.0package.json
npmcli-tableau2.0.1package.json
npmcommander2.15.1package.json
npmcroner4.1.97package.json
npmdayjs1.11.15package.json
npmdebug4.4.3package.json
npmeventemitter26.4.9package.json
npmfast-json-patch3.1.1package.json
npmjs-yaml4.3.0package.json
npmpidusage4.0.1package.json
npmpm2-deploy1.0.2package.json
npmproxy-agent6.5.0package.json
npmsemver7.7.2package.json
npmtx21.0.5package.json
npmws8.21.0package.json
All dependencies 29

Full resolved dependency set from the GitHub dependency graph: 22 direct and 7 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@pm2/blessed0.1.81direct
npm@pm2/js-api0.8.1direct
npm@pm2/pm2-version-check1.0.4direct
npmamp0.3.1direct
npmamp-message0.1.2direct
npmansis4.0.0-node10direct
npmasync3.2.6direct
npmchokidar3.6.0direct
npmcli-tableau2.0.1direct
npmcommander2.15.1direct
npmcroner4.1.97direct
npmdayjs1.11.15direct
npmdebug4.4.3direct
npmeventemitter26.4.9direct
npmfast-json-patch3.1.1direct
npmjs-yaml4.3.0direct
npmpidusage4.0.1direct
npmpm2-deploy1.0.2direct
npmproxy-agent6.5.0direct
npmsemver7.7.2direct
npmtx21.0.5direct
npmws8.21.0direct
npmexpress^4.16.2indirect
npmexpress^4.21.0indirect
npmmocha*indirect
npmmocha^11.7.0indirect
npmpmxbetaindirect
npmshould*indirect
npmshould^13.2.3indirect
Dependency advisories 1

Installing npm:pm2@7.0.3 pulls in 77 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
js-yaml4.3.0directhigh14.3.1

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.