vercel/ms
main · 4ff48cePublicCached · audited 10 September 2026vercel/ms passes every install, build, quickstart, and CI-parity gate with 100% test coverage across Node and Edge runtimes, but its agent-readiness inventory sits at just 26%, and thrown errors carry no codes or documented recovery guidance.
The core loop of vercel/ms — install, build, and 167 passing tests across Node and Edge — is fast, reproducible, and gate-clean, reflecting a mature, simple library. The debt is concentrated in operability surfaces: no AGENTS.md or machine-readable schema, no error codes or troubleshooting links on thrown errors, no --json or structured-output guidance, and no CONTRIBUTING or architecture doc. None of these block a human user today, but they slow autonomous agents and new contributors.
What we ran
Nine areas
Findings
One, ranked by severity. Every one carries the command that proves it and a prompt that closes it.
Thrown errors have no codes, links, or troubleshooting guidance
ms() and format() throw plain Error objects with only a short message and no error code, documentation link, or recovery guidance, e.g. at src/index.ts:59 and src/index.ts:227. A caller hitting these in production has no structured way to distinguish or handle them programmatically.
Each thrown Error in src/index.ts carries a stable code property and README documents each code with cause and fix; a test asserts on error.code.
Hard gates
A gate is a defect serious enough that no average can wash it out. One fired gate makes the verdict FAIL, whatever the number says.