PUBLIC NOTICE · AUGUST 26, 2026

Breaking npm coverage change

We apologize for changing the meaning of npm coverage without a prominent public notice.

On August 26, 2026, this service replaced its 4.3-million-package npm registry crawl denominator with a 2,295-package ecosyste.ms critical subset. The former crawl had reached 218,774 packages in the public checkpoint and 221,774 in the local checkpoint. The current “100%” indicator refers only to the 2,295-package critical subset; npm overall is not 100% covered.

This breaking change narrowed the active npm crawl population and broke comparison with earlier progress. A missing npm result is not proof that no npm package uses that executable name. The project tracks restoration of broader, multi-source npm coverage in Issue #54; the previous crawl evidence remains in Issue #42.

PUBLIC INDEX · READ-ONLY PLAYGROUND

Find out whether a command name is already in use.

Query the same executable evidence that powers the MCP server. Watch registry coverage move forward, then test a lookup without installing anything.

Try a query ↘ View dataset metadata

SnapshotLoading…canonical dataset

Executable namesLoading…indexed canonical names

Registry sweepLoading…latest crawl status

Next CI registry refreshLoading…every six hours · minute 17 UTC

01 / COVERAGE CONTROL ROOM

Registry progress

Loading crawl report…

◷

Next CI registry refreshThe page is redeployed after CI publishes crawl progress.

OS packages · file indexes

Language registries · package artifacts

C and C++ recipe repositories · snapshots

Evidence-based completion forecast Calculating… Reading published checkpoints.

Registry progress: —
Go remaining: —
Net backlog / day: —
Observed window: —

LIVE REQUEST

check_executable

STATIC JSON

Response

Select an operation and run a query.

Not covered: PowerShell. Its cmdlets are out of scope — Verb-Noun names do not occupy the namespace a CLI is named in.