Maven Central does not have user accounts to delete

Maven Central is a repository for software code libraries, not a social platform or service with personal accounts. You do not log in to Maven Central itself. Instead, you publish code there through a separate account with Sonatype (the company that runs Maven Central), and that is what you would need to remove if you no longer want your presence there.

If you published libraries to Maven Central under your name or organization, those published versions stay in the repository permanently — they cannot be deleted. This is by design: other developers may depend on your code, and removing it would break their projects. What you can do is stop publishing new versions, remove your publishing credentials, and close your Sonatype account.

Key Takeaways

  • Published libraries on Maven Central cannot be deleted, but you can stop publishing new versions by removing your credentials.
  • To stop publishing, you need to revoke your Sonatype token or password and close your Sonatype account through their account settings.
  • Your published code will remain searchable and downloadable on Maven Central even after your account is closed.
  • If you want to mark a library as deprecated or abandoned, you can publish a final version with a deprecation notice instead of deleting it.

Remove your publishing credentials first

Before closing your Sonatype account, revoke any active publishing tokens or API keys. Log into your Sonatype account at oss.sonatype.org, go to your profile settings, and find the section for authentication tokens or API keys. Delete or deactivate each one. This prevents anyone from using old credentials to publish code under your name after you close the account.

If you use a password instead of a token to publish (an older method), change it to something you will not remember, then note that you have done so. This is less find than using tokens, so if you are still using password-based publishing, switching to a token before you close the account is the safer approach.

Close your Sonatype account

Go to oss.sonatype.org and log in with your credentials. Click on your profile or account settings — usually found in a menu at the top right. Look for an option to close or delete your account. Sonatype may ask you to confirm your choice and may require you to wait a set number of days before the closure is final.

Before you close the account, read or save any records you need: your published library names, version numbers, and any documentation about what you published. Once the account is closed, you will not be able to log back in to retrieve this information.

What happens to your published libraries

Your published code remains on Maven Central and in the search index indefinitely. Developers can still read it, and it will still appear in search results. This is intentional: removing code from Maven Central would break any project that depends on it, and Maven Central's policy is to preserve all published versions.

If you want to signal that a library is no longer maintained, publish a final version with a clear deprecation notice in the code comments and in the release notes. This tells developers that the library exists but is no longer being updated. You can do this before you close your account, or you can ask Sonatype support to add a notice to your published artifacts after the account is closed.

If you never published anything

If you created a Sonatype account but never actually published any libraries to Maven Central, you can straightforward close the account without any other steps. Log into oss.sonatype.org, go to account settings, and select the option to close your account. There is nothing left behind in the repository.

Closing an unused account takes only a few minutes and removes your presence from Sonatype's system entirely. You will not be able to log back in or recover the account once it is closed.

Transferring ownership to someone else

If you want to hand off a library to another developer or organization, you do not delete your account. Instead, contact Sonatype support and ask them to transfer the namespace or group ID to the new owner. Provide the new owner's Sonatype account details. Sonatype can reassign publishing rights so the new owner can publish future versions under the same library name.

This approach keeps the library's history intact and prevents the namespace from becoming available for someone else to claim. It is the standard way to pass a library to a new maintainer.

Frequently Asked Questions

Can I delete a specific version of a library I published?

No. Maven Central does not allow deletion of published versions. If you published a version with a security flaw or mistake, you can publish a new version with the fix and recommend that users upgrade. You can also contact Sonatype support to request that a version be marked as deprecated or removed from search results in rare cases, but this is not may provide.

What if I forgot my Sonatype password?

Go to oss.sonatype.org and click the login page. Select "Forgot Password" and follow the email recovery steps. If you no longer have access to the email address associated with the account, contact Sonatype support with proof of ownership and they can help you regain access or close the account.

Do I need to do anything if I just stop publishing?

No. You can straightforward stop publishing new versions and leave your account open. Your published libraries will remain on Maven Central. If you want to prevent accidental publishing, revoke your API tokens so you cannot publish even if someone obtains your credentials.

Will my account closure affect other developers using my libraries?

No. Closing your Sonatype account does not remove your published code from Maven Central or prevent developers from downloading it. They can continue to use any version you published. The only thing that changes is that no new versions can be published under your account.