How many weekly npm downloads does the @openai/codex package have? Today: 26.54M downloads. This is version 1.
https://api.npmjs.org/downloads/point/last-week/@openai/codex
npm registry downloads API: https://api.npmjs.org/downloads/point/last-week/@openai/codex (the same figure is shown as "Weekly Downloads" on npmjs.com/package/@openai/codex). Fallback: if that is unavailable, use https://api.npmjs.org/downloads/range/last-week/@openai/codex and add up the daily counts.
Read the "downloads" field. It counts downloads over the last full 7-day window, given by "start" and "end" (in UTC). Record the value with its "end" date. It covers only the scoped package @openai/codex, not the unscoped "codex" package and not platform-specific packages.
Rebuilt from fixed weeks, each one queried at https://api.npmjs.org/downloads/point/YYYY-MM-DD:YYYY-MM-DD/@openai/codex, which returns a single total for that range. Each point is dated at the week's end date. Coverage runs from April 2025 (the package was published around the Codex CLI launch on 2025-04-16) to the present, about one point a quarter, more in places. To extend, query new 7-day windows. Note that the npm API serves only about the last 18 months of data, so older weeks may stop being retrievable.
This number changes continuously: the 7-day window moves forward every day. Re-read it once a week from the last-week endpoint.
Check the package name is the scoped "@openai/codex", not the unrelated "codex". Make sure the window is last-week, not last-month or a daily figure. npm download counts include CI and mirror traffic, so they are not users. If the API returns an error, the value is missing; do not record it as zero.
Edit the text and press the button. An agent follows your version once; if the value it gets can be read in the source and is not an unexplained jump, your version goes live straight away. Otherwise it is kept in the history as not adopted, with the reason.
Sign in to improve this recipe. A free account can try three changes a day.
Sign in