GitHub

nightwatch

Easy to use Node.js based end-to-end testing solution for web applications using the W3C WebDriver API.

npm says

138,964

per week

Every tarball fetch: mirrors, scanners, CI and people.

real installs

high confidence

≈ 138K–139K

per week

best guess 139K

Mirror spikes and crawlers removed. CI and dependency installs still count, so this is not a head count.

About 0% of npm's count looks like noise. noise real installs

Why this estimate

With JavaScript on, this lists what the filter found for this package.

Most used major version: 3, the latest one, with 49% of last week's downloads above the crawler floor. Most used single version: 3.16.0.

Snapshot from the daily build of Nov 6, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.

How many people use nightwatch?

npm counted 138,964 downloads of nightwatch in the last 7 days. Nobody can count people exactly, npm included: it does not record who downloaded what. After removing mirror spikes and crawlers, about 138K–139K look like real installs. Noise is under 1% of npm's count. What remains still includes CI and installs as a dependency of other packages.

Is nightwatch still maintained?

Most likely yes, going by its releases. The latest version, 3.16.0, came out on May 25, 2026. The last 12 months saw 4 stable releases, typically 29 days apart. It was first published on Jan 3, 2014. npm lists 4 maintainers.

Is nightwatch still used?

Downloads with publish spikes removed are up 20% over 3 months and up 8% over 11 months. For scale, the median of the 269 packages we track, which lean towards today's most downloaded, is up 157% over 11 months, so this one is behind that. Last week, 49% of downloads above the crawler floor were on major version 3, the latest one; the most used single version was 3.16.0, with 16%. Weekdays get 1.5× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 1,464 downloads a week, roughly 4 per version.

How the estimate works

  1. Cut the spike every new version gets from mirrors in its first days.
  2. Subtract the flat floor robots download from every version each week.
  3. Show what is left as a range, with a confidence level. It still includes CI and dependency installs, so it is not a count of people.

Read the methodology

Other packages