Maven Central publishing limits: what high-volume publishers need to know - Central Repository - Sonatype Community

-->

My Sonatype

Community

Forum

Ideas

Office Hours

Learn

Courses

Videos

Support

Knowledge Base

Documentation

Resources

SSC Maturity Survey

STEPP Assessment

Hosted Workshops

Maven Central publishing limits: what high-volume publishers need to know

Central Repository

andres<br>(Andrés Pérez)

June 16, 2026, 1:54pm

Hi everyone,

Maven Central is critical infrastructure for the Java ecosystem: a shared place where open source projects publish release-ready components and millions of developers reliably consume them.

Sonatype is introducing publishing limits for high-volume Maven Central publishers. These limits are designed to distinguish community-scale open source publishing from commercial-scale or infrastructure-driven publishing through Maven Central, while preserving free publishing for the vast majority of the open source community.

This is part of a broader shift across public package infrastructure. Registries that were originally built for community-scale software sharing are increasingly being used as production infrastructure by commercial platforms, automated systems, CI/CD pipelines, scanners, and machine-driven software supply chains.

A maintainer publishing normal releases for an open source project is one thing. An organization using Maven Central as the last-mile distribution channel for SDKs, generated clients, agents, integrations, or other commercial software components is another. Publishing size and frequency are not perfect measures of intent, but they are practical signals that a publishing pattern may be serving a different purpose than ordinary open source project releases.

That distinction shows up clearly in recent publishing activity. Over the past 90 days, 10% of namespaces accounted for:

more than 88% of all files published to Maven Central

more than 90% of total storage consumed by new releases

over 70% of all new release events

That concentration does not mean every high-volume namespace is commercial, or that every open source project with unusual publishing patterns is doing something wrong. It does show why publishing limits need to focus on sustained high-volume patterns rather than treating all publishing activity as equivalent.

Starting June 16, 2026 , Maven Central will begin the first phase of this rollout. All publishers will see an announcement in Maven Central explaining the upcoming publishing limits. Publishers whose organizations are approaching or exceeding the monthly publishing limits will also see usage-specific notifications.

During this initial phase, publishing will not be blocked, throttled, or prevented. The goal is to give affected publishers time to review their usage, understand their publishing patterns, and plan ahead before enforcement begins.

Most Maven Central publishers will not need to make any changes. This is not a blanket fee for publishing to Maven Central. The change is focused on organizations with unusually large artifacts, very high publishing frequency, repeated high-volume publishing activity, or other patterns that indicate commercial-scale use.

For organizations above the free publishing limits, there are three paths:

1. Reduce avoidable publishing activity

Maven Central should be used for public distribution of release-ready artifacts, not as the default destination for every intermediate output produced by a software factory. Avoid publishing every CI build, move internal-only artifacts to private repositories, and review automation for duplicate or unnecessary publish attempts.

Request an exemption for review

Some legitimate open source projects may have unusual publishing patterns, unusually large artifacts, or release models that deserve review. Exemptions are expected to be rare, but the process exists for cases where publishing volume alone does not tell the whole story.

Move to Maven Central Publisher Pro

Maven Central Publisher Pro is the paid path for organizations with higher-volume, commercial-scale, or infrastructure-driven publishing needs. It allows those organizations to publish at a higher scale while helping support the infrastructure their publishing patterns depend on.

Enforcement is scheduled to begin on August 11, 2026. Starting then, organizations above the free publishing limits will have publishing activity capped until usage is reduced, an exemption has been approved, or a paid option is in place.

Publishers can review their organization and namespace-level usage in Usage Center, including file count, release size, and release frequency. Usage Center is the source of truth for whether an organization is within or above the free limits.

For important dates, guidance on next steps, and further reading, visit the Maven Central Publishing Limits page:

https://central.sonatype.org/publish/maven-central-publishing-limits/

Maven Central was built for open...