Compare

GitHub vs npm

npm scores higher on the AgentReady, 57/100 against 55/100. They differ on 17 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

GitHub. GitHub is a platform where developers, agents, and code come together for collaboration.

npm. npm is the package manager for JavaScript and the world's largest software registry, owned by GitHub.

Where GitHub is ahead

GitHub passes clear canonical domain, clear product positioning, llms.txt published and llms-full.txt / full agent docs, and npm does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds adopt: agent-compatible signup flow. npm misses it.

And on operate, structured, predictable output, rate-limit behavior predictable and observable execution. npm misses those.

Where npm is ahead

npm passes machine-readable metadata, and GitHub does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: structured api reference and pricing understandable. GitHub misses those.

And on adopt, self-service signup, no mandatory sales call, free trial or free allowance, fast time to first request and copyable quickstart. GitHub misses those.

Finally, on operate, agent compatibility verified. GitHub misses it.

What neither does

Both fail openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, programmatic credential creation, machine-readable errors, retry behavior documented, idempotency support. If your agent needs any of those, you will be building it yourself either way.

Score, pillar by pillar

The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.

Discover. GitHub leads 93 to 67. GitHub misses machine-readable metadata; npm misses clear canonical domain, clear product positioning, llms.txt published, llms-full.txt / full agent docs.

Understand. npm leads 38 to 15. GitHub misses structured api reference, openapi / spec quality, authentication documented, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; npm misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt is whether an agent can get a key and make its first successful call without a human in the loop. npm leads 80 to 52. GitHub misses self-service signup, no mandatory sales call, programmatic credential creation, free trial or free allowance, fast time to first request, copyable quickstart; npm misses agent-compatible signup flow, programmatic credential creation.

Operate. GitHub leads 59 to 41. GitHub misses machine-readable errors, retry behavior documented, idempotency support, agent compatibility verified; npm misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution.

Pricing

GitHub does not publish a machine-readable starting price. npm starts at $7/mo and has a free tier.

Signal by signal

Which to pick

npm clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: GitHub and npm. Alternatives to each: GitHub, npm.

An agent can fetch this as data: POST /v1/compare {"slugs": ["github", "npmjs"]}