JavaScript package manager benchmarks

Install and run times for JavaScript tools, measured nightly on identical runners and published in full, failures included.

Registries Package managers Task runners

Set up your agent

Every page on this site is also available as Markdown, and /llms.txt indexes them all. Paste this prompt into your agent to point it at the benchmarks:

Agent prompt

Help me use the vlt benchmarks. Start by reading https://benchmarks.vlt.io/llms.txt, which lists every page of the site and explains how to read the results. Every page is available as Markdown: append .md to its URL, or request the page with an Accept: text/markdown header. Query parameters apply to the Markdown as they do to the page: https://benchmarks.vlt.io/package-managers/clean.md?fixture=babylon is that scenario on one fixture. https://benchmarks.vlt.io/llms-full.txt holds every scenario of the latest run, at the default view, in one file.

1. For structured data, use the JSON API, described at https://benchmarks.vlt.io/openapi.json: /api/v1/runs, /api/v1/catalog, /api/v1/{section}/{scenario} (the full report, same parameters as the page) and /api/v1/{section}/{scenario}/history (the trend, failures and coverage).
2. To query it as tools, add the read-only MCP server with `claude mcp add --transport http vlt-benchmarks https://benchmarks.vlt.io/mcp`. Its tools are list_benchmarks, get_results, get_history and compare_scenarios.
3. When you report a result: total time is the measurement and the ranking. A DNF (the run exited non-zero) is never counted as a time, a tool that did not complete every fixture is not ranked against tools that did, and derived metrics are labelled "derived".

Only quote numbers that appear on the site, and name a run by its date.