Yes — it's read live from Maven Central, the primary registry for Java and JVM libraries.

No. This is a fully key-less public API.

How often does it refresh?

The pipeline polls for new records every few minutes.

Yes — free, no download, in your browser.

It is the namespace of the publisher, typically a reversed domain name, that groups related artifacts. Publishers have to verify control of the namespace before they can publish under it.

Can a published version be changed?

No. Maven Central does not modify components once they are public, so a fix requires a new version number.

Why do I see runs of similar rows?

Projects made up of several modules often release them together, so one release can produce many artifacts with matching versions.

Maven Central New Releases Screensaver

The Maven Central New Releases screensaver streams real newly-published Maven Central artifact versions as they're reported. It is free, runs in your browser, and ESC exits.

How the Maven Central New Releases screensaver works

The background pipeline polls Maven Central — the primary registry for Java and JVM libraries — every few minutes for new records.

Each new item eases up into its slot at the bottom of the list as it arrives.

A header shows a live/connecting indicator and the last update time.

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

How Maven Central identifies releases

Maven Central is the main public repository for Java and other JVM libraries, operated by Sonatype. Build tools such as Maven and Gradle fetch dependencies from it, and every component is identified by three coordinates: a groupId, usually a reversed domain name like org.apache.commons, an artifactId naming the library, and a version. The saver’s rows are those coordinates, shown as they are published.

Central’s policy is immutability: components are not removed or modified once they are publicly available, which keeps builds that depend on them reliable. If a published component has a bug, the recommended fix is to publish a new version. Versions ending in -SNAPSHOT, reserved for in-development builds, cannot be published there. Every deployed file must carry a GPG signature, and the POM must supply details such as a name, description, licence and developer information.

Publishers must also verify the namespace they publish under, for example by proving control of the matching domain with a DNS record, or by using an io.github. namespace verified through GitHub. Large projects often release several artifacts together, so one project can account for a run of rows with the same group and similar version numbers. Being on Central shows an artifact was published, not that it has been audited or is still maintained.

A worked example

A real recent item scrolls into view with its details, then eases upward as newer ones arrive behind it.

Settings & tips

Each release shows the real group, artifact and version coordinates.
Accent recolours the header and highlights.
Maven Central is the primary registry for Java and JVM libraries.

Frequently asked questions

Is this real data?: Yes — it's read live from Maven Central, the primary registry for Java and JVM libraries.
Is a key needed?: No. This is a fully key-less public API.
How often does it refresh?: The pipeline polls for new records every few minutes.
Is it free?: Yes — free, no download, in your browser.
What is a groupId?: It is the namespace of the publisher, typically a reversed domain name, that groups related artifacts. Publishers have to verify control of the namespace before they can publish under it.
Can a published version be changed?: No. Maven Central does not modify components once they are public, so a fix requires a new version number.
Why do I see runs of similar rows?: Projects made up of several modules often release them together, so one release can produce many artifacts with matching versions.

← All Technology & Developer screensavers