How pnpm’s scores are calculated

The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.

verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10

PA Score26/100

Agent-ready 37.8 × 0.30 = 11.34

API quality 0.0 × 0.20 = 0.00

Openness 0.0 × 0.20 = 0.00

Built-in AI n/a — excluded, its ×0.15 weight renormalized away

Automation 70.0 × 0.15 = 10.50

(11.34 + 0.00 + 0.00 + 10.50) ÷ (0.30 + 0.20 + 0.20 + 0.15) = 21.84 ÷ 0.85 = 25.7 — weights renormalized over the scored components

Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.

Agent-ready37.8/100×0.30 of the PA blend

Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

[probe] https://pnpm.io/llms.txt“PROBE llms.txt: HTTP 404 at https://pnpm.io/llms.txt”
[probe] https://pnpm.io/motivation.md“PROBE docs-md: HTTP 404 at https://pnpm.io/motivation.md”
[probe] https://pnpm.io/openapi.json“PROBE openapi: all candidate paths 404 (https://pnpm.io/openapi.json, https://pnpm.io/swagger.json, https://pnpm.io/api/openapi.json, https://pnpm.io/.well-known/openapi.json)”

Run the product headlessly / in CI for automationweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

[claimed-docs] https://pnpm.io/continuous-integration“When pnpm detects that it is running in CI, it switches to frozen-lockfile mode automatically.”
[claimed-docs] https://pnpm.io/continuous-integration“It needs no Node.js. pnpm is a self-contained executable, and it can install the runtime for you afterwards with `pnpm runtime set node lts -g`”
[claimed-docs] https://pnpm.io/continuous-integration“If your `package.json` has a `packageManager` or `devEngines.packageManager` field, pnpm switches to that version on first use”
[claimed-docs] https://pnpm.io/continuous-integration“It needs no Node.js. pnpm is a self-contained executable, and it can install the runtime for you afterwards with pnpm runtime set node lts -g”
[claimed-docs] https://pnpm.io/cli/install“In a CI environment, installation fails if a lockfile is present but needs an update.”
[community] https://news.ycombinator.com/item?id=30919487“It works very fast in CI, its cache is smaller and it builds node_modules much faster... Speed difference is 15s vs 35s for our use case which is pretty significant.”

Plug MCP servers into this product so it can use their toolsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Connect an agent via an official MCP serverweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Use an official CLIweight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

[probe] https://pnpm.io/pnpm-cli“official CLI documented at https://pnpm.io/pnpm-cli”
[claimed-docs] https://pnpm.io/cli/install“Run a full dependency resolution and report what a real install would change, without writing anything to disk.”
[claimed-docs] https://pnpm.io/cli/audit“Verifies the ECDSA registry signatures of installed packages against the public keys published by each registry at `/-/npm/v1/keys`.”
[claimed-docs] https://pnpm.io/cli/audit“Checks for known security issues with the installed packages.”
[community] https://news.ycombinator.com/item?id=30919487“pnpm has been my goto JS monorepo package manager + script runner for a couple of years now. IMO it has almost zero downsides and huge upsides.”
[community] https://news.ycombinator.com/item?id=30919487“It works very fast in CI, its cache is smaller and it builds node_modules much faster... Speed difference is 15s vs 35s for our use case which is pretty significant.”

Drive the product through a documented public APIweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

[probe] https://pnpm.io/llms.txt“PROBE llms.txt: HTTP 404 at https://pnpm.io/llms.txt”
[probe] https://pnpm.io/motivation.md“PROBE docs-md: HTTP 404 at https://pnpm.io/motivation.md”
[probe] https://pnpm.io/openapi.json“PROBE openapi: all candidate paths 404 (https://pnpm.io/openapi.json, https://pnpm.io/swagger.json, https://pnpm.io/api/openapi.json, https://pnpm.io/.well-known/openapi.json)”
[probe] https://pnpm.io/pnpm-cli“official CLI documented at https://pnpm.io/pnpm-cli”

Issue scoped/least-privilege API credentials for an agentweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Build against official SDKsweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Subscribe to events via webhooksweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Agent-ready = 34.0 ÷ 90 × 100 = 37.8

API quality0.0/100×0.20 of the PA blend

The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

[probe] https://pnpm.io/llms.txt“PROBE llms.txt: HTTP 404 at https://pnpm.io/llms.txt”
[probe] https://pnpm.io/motivation.md“PROBE docs-md: HTTP 404 at https://pnpm.io/motivation.md”
[probe] https://pnpm.io/openapi.json“PROBE openapi: all candidate paths 404 (https://pnpm.io/openapi.json, https://pnpm.io/swagger.json, https://pnpm.io/api/openapi.json, https://pnpm.io/.well-known/openapi.json)”

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Test against a sandbox environment without touching production dataweight 1

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

[community] https://hn.algolia.com/api/v1/items/49460032“Am I the only one that hates the decision to no longer support corepack?”

API quality = 0.0 ÷ 40 × 100 = 0.0

Openness0.0/100×0.20 of the PA blend

Can you leave, inspect, or self-host — data export, open source, portability.

Do everything through the API that I can do in the UIweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Export all of my data in open formats and leaveweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Read the product's source under an open licenseweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Self-host the core productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Openness = 0.0 ÷ 20 × 100 = 0.0

Built-in AIn/a×0.15 of the PA blend

Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.

Get AI-generated insights and suggestions from my data inside the productweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Set up automations that run autonomously in the backgroundweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Delegate tasks to a built-in AI assistant inside the productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Operate the product with natural-language commandsweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

every cell n/a — unscored (not zero), excluded from the blend

Automation70.0/100×0.15 of the PA blend

Depth of automation primitives — rules, scheduling, bulk operations, webhooks.

Perform bulk operations across many items at onceweight 2

2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max

[claimed-docs] https://pnpm.io“First-class monorepos: the workspace protocol for local packages, filtering to run tasks on just the projects you touched, and a single lockfile for everything.”
[claimed-docs] https://pnpm.io“Define a dependency version once in pnpm-workspace.yaml and reference it as "catalog:" everywhere. One line to upgrade, and no more version-drift merge conflicts.”
[claimed-docs] https://pnpm.io/settings“Allows setting project-specific configuration for individual workspace packages. This replaces workspace project-specific `.npmrc` files.”
[community] https://news.ycombinator.com/item?id=30919487“we're part way through switching all our monorepos from lerna to pnpm & simply could not be happier & more excited... everything on pnpm's built-in monorepo support just works, nice & easy & fast.”
[community] https://news.ycombinator.com/item?id=30919487“I recently migrated a fairly large monorepo (20+ packages) that used Lerna and npm to pnpm... Dependency install times went down by a huge amount... We even noticed that the size of some of our production bundles went down.”

Define rules that trigger actions automatically on eventsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Schedule recurring jobs or workflowsweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Version, review, and roll back my automationsweight 1

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Automation = 14.0 ÷ 20 × 100 = 70.0