Is this real npm data?

Yes — real package updates from npm's own replication feed.

No. The replication feed is fully key-less.

Does this show package contents?

No — it shows real package names as they update, not their code.

Yes — free, no download, in your browser.

What is a scoped package?

A package whose name starts with @ followed by a scope and a slash, as in @scope/package-name. The scope is a namespace tied to an npm user or organisation, which lets different owners use the same package name without conflict.

What does the sequence number mean?

It is a position in the registry's CouchDB changes log. Tools remember the last one they saw and ask for changes after it, so they can resume without missing anything.

Is every package shown safe to install?

No. The feed only records that something changed in the registry. Anyone can publish a package, so entries are not reviewed or vetted.

npm Live Package Update Stream Screensaver

The npm Live Package Update Stream screensaver shows real package updates landing on the npm registry right now. It is free, runs in your browser, and ESC exits.

How the npm Live Package Update Stream screensaver works

The saver reads real recent changes from npm's own replication _changes feed.

Each entry shows a real package name as it's updated or published.

The pipeline saves its position so each run picks up new real updates since the last one.

No key is required for this key-less public endpoint.

The npm registry and its changes feed

npm is the package registry for the JavaScript ecosystem, run by GitHub, which is part of Microsoft. Developers publish packages there as reusable libraries and tools, and others install them with a command line client. The dependency tree behind even a small web project can be large, which is one reason registry activity is constant.

The registry is, at its core, a CouchDB application, and CouchDB exposes a changes feed: an ordered log of document changes. Each change carries a sequence value, and a consumer can resume from the last one it saw, which lets mirrors and analysis tools follow the registry without repeatedly downloading everything. The name on each entry is the package that changed. Scoped packages are written @scope/package-name, where the scope is a namespace tied to an npm user or organisation.

An entry means that a package record changed, for example because a new version was published or its metadata was edited. It says nothing about what the update contains or whether it is safe. Any publisher can upload a package, so a busy stretch includes experiments and test uploads alongside serious releases, and a name appearing here should never be treated as a vetted release.

A worked example

A real package name updated moments earlier scrolls past exactly as it landed in npm's real replication log.

Settings & tips

Package names are real, unfiltered npm registry activity.
Accent recolours the ticker text.
The npm registry hosts real JavaScript packages used worldwide.

Frequently asked questions

Is this real npm data?: Yes — real package updates from npm's own replication feed.
Is a key needed?: No. The replication feed is fully key-less.
Does this show package contents?: No — it shows real package names as they update, not their code.
Is it free?: Yes — free, no download, in your browser.
What is a scoped package?: A package whose name starts with @ followed by a scope and a slash, as in @scope/package-name. The scope is a namespace tied to an npm user or organisation, which lets different owners use the same package name without conflict.
What does the sequence number mean?: It is a position in the registry's CouchDB changes log. Tools remember the last one they saw and ask for changes after it, so they can resume without missing anything.
Is every package shown safe to install?: No. The feed only records that something changed in the registry. Anyone can publish a package, so entries are not reviewed or vetted.

← All Technology & Developer screensavers