Self-hosted service
sonatype/nexus-public avatar
sonatype/nexus-public

Nexus Repository Core: three formats, an embedded H2, and a build recipe pinned to an older tag

Sonatype Nexus Repository Open-source codebase mirror

2,710 stars759 forksJavaEPL-1.0

At a glance

What is it?
sonatype/nexus-public holds the open source Core of Sonatype's binary repository manager: maven, raw and APT formats on an embedded H2 database, with npm, Docker, NuGet and PyPI left to a separate Community Edition binary. Building it means Java 21, Node, corepack and a pinned Yarn, and the first start writes default administrator credentials to disk.
Who is it for?
sonatype/nexus-public is worth building only when you need the maven, raw and APT path on a small workload and want to own the assembly yourself; the format coverage most teams want is a binary download instead.
Can I use it commercially?
Yes, with conditions. EPL-1.0 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
Is it still maintained?
Yes. The repository last received commits 10 days ago.
What is it written in?
Mainly Java, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • sonatype/nexus-public2,710 ★ · +48
Star history
Repository2026-10-042026-11-15
sonatype/nexus-public2.7k2.7k

48 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Core covers maven, raw and APT, and sends every other format to a binary download

The scope statement is short and load bearing: this is the open source codebase of Nexus Repository Core, containing functionality for the maven, raw and APT repository formats, running on an embedded H2 database that the project describes as appropriate for small workloads. Everything else people associate with the product sits in a different artifact. The README points to a Community Edition binary download that adds npm, Docker, NuGet, PyPI and many other formats, and that also permits an external PostgreSQL database, which is what the Kubernetes deployment story rests on. So the tree you can build here is the small edition: three formats, one embedded database, no external database option. Anyone arriving for npm or Docker support has to change which artifact they run, not which flag they pass.

The one line description says mirror, and the README says Core

The repository is described in a single line as the Sonatype Nexus Repository open-source codebase mirror. The README calls the same tree the Core codebase and titles it Sonatype Nexus Repository Core. Mirror suggests a copy kept in step with an upstream that lives somewhere else, while the README describes a source tree you compile yourself with Apache Maven and Java 21, assemble into a directory, and start as a jar. Nothing in the listing settles which reading is correct, and there is no submodule or vendor pointer to an upstream private repository. The word mirror is the only place the two descriptions pull apart, so decide between building from source and downloading a binary on the README's version, which is the one the assembly path, the profile name and the license header all agree with.

The yarn workspace list points into a private/ directory the root listing does not show

The frontend build is wired through package.json, which pins the package manager to [email protected] and declares four workspaces: three under public/common/components, for nexus-ui-plugin, nexus-rapture and nexus-coreui-plugin, and a fourth at private/cloud/components/nexus-cloudui-plugin. The root listing contains one source directory, public/, and no private/. A workspace path that is not present in the published tree is something the Yarn install still has to resolve, and the README says nothing about how that path is handled when the directory is absent. The same file pins exact versions for a long list of transitive packages through resolutions, including tmp, node-gyp and sha.js, while one direct dependency, @react-hook/resize-observer, keeps a caret range. Two linters are configured side by side at the root, biome.json and eslint.config.mjs.

Java 21 and corepack sit in front of the Maven build, with yarn pinned exactly

Getting a jar out of this tree takes three toolchains in sequence. Maven wrapper scripts are included, so Maven itself is not the obstacle, and Java 21 is the stated requirement. Before Maven runs, the workspaces have to be initialized for the frontend modules: enable corepack, which the README notes ships with Node.js 16.10 or newer, then install the workspace dependencies through corepack.

shell
# Enable corepack (ships with Node.js 16.10+)
corepack enable

# Install workspace dependencies
corepack yarn install

The build itself is one command with a profile name attached:

shell
./mvnw clean install -Ppublic

The profile is called public, the same word that appears in the self-hosted assembly path further down. Because the package manager is pinned to an exact version rather than a range, the Node install you bring has to ship a corepack that can produce that version.

Default administrator credentials, database and blobstore all land in sonatype-work

The running instructions say the application creates a sonatype-work directory at public/selfhosted/assemblies/nexus-repository-core/target/sonatype-work, and that this directory holds the default administrator credentials, the database and the file blobstore. Three things follow from that one sentence. The credentials land on disk in the working directory at first start, so the admin account is only as private as the permissions on that path. The database is the embedded H2 file, which is the same limit named in the scope statement when H2 is called appropriate for small workloads. The blobstore is a local directory, so stored artifacts sit wherever the process was pointed. The README does not document changing those credentials before first start, and does not describe moving the blobstore off local disk.

The run step globs the jar name and the assembly path runs four directories deep

To start what you built you navigate to public/selfhosted/assemblies/nexus-repository-core/target/assembly and run the jar through a wildcard: java -jar bin/nexus-repository-core-*.jar. The wildcard means the command starts whatever the assembly put in bin/, so a build that leaves more than one jar there lets the shell pick, and no filename is pinned to compare against. The path itself encodes the module layout: a self-hosted assembly nested under public, then assemblies, then nexus-repository-core, then target. Anything scripted, a container image or a service unit, has to hard code that path, and a unit file cannot expand the wildcard the way a shell does. The same target directory is where sonatype-work appears, so build output and runtime state end up under one parent.

The build recipe names release-3.89.0-09 while the tags now run to release-3.96.4-01

Released versions are tagged and branched as release-{version}, and the worked example is a specific old tag.

shell
git fetch --tags
shell
git checkout -b release-3.89.0-09 origin/release-3.89.0-09 --

That example sits several minor versions behind the published line: release-3.96.2-01 on 2026-09-18, release-3.96.3-01 on 2026-09-22 and release-3.96.4-01 on 2026-09-30, all built under the same Java 21 requirement and the same profile. The recipe is not wrong, it is just older than the tags, and it is the only tag anyone is shown. Two dates are worth holding side by side: the last push on the default branch is 2026-09-22, which is the publication date of release-3.96.3-01, while the newest release is dated eight days later. Whether that tag came from an earlier commit is not stated, so check which commit your build came from.

Two download links point at two editions, and support is split by tier

The homepage field for the project points at the Repository OSS download page, while the README sends readers to the Community Edition download when they want the fully featured version. That is a small difference, but it means the link a package index or a badge shows and the link the documentation recommends are not the same destination. Support is divided the same way: Pro customers are pointed at a support address, everyone else at the issue tracker, the Sonatype Community forum for tips, and a separate address for reporting a security vulnerability. The project is not archived, its last push on the default branch is 2026-09-22, and the tracker carries 375 open issues against 2655 stars. That is the state a self-hoster inherits with the code: the answers live in the tracker and the forum, not in the README.

Editorial conclusion

sonatype/nexus-public is worth building only when you need the maven, raw and APT path on a small workload and want to own the assembly yourself; the format coverage most teams want is a binary download instead. Before you commit, settle four things: which edition your workloads actually need, whether Java 21 plus a Node with corepack are available for the Yarn step, what you will do about the default credentials written into sonatype-work on first start, and which commit your build came from, since the recipe in the README still names a tag from an older line. Compiling this tree gives you a repository manager you can patch. Downloading the Community Edition gives you the formats and the external database without the build at all.

Frequently asked questions

Is sonatype/nexus-public the same thing as the Community Edition download?

No. This is the open source codebase of Nexus Repository Core, which holds the maven, raw and APT formats on an embedded H2 database. The Community Edition is a separate binary that adds npm, Docker, NuGet, PyPI and other formats, and allows an external PostgreSQL database.

What does it take to build sonatype/nexus-public from source?

Apache Maven through the included wrapper script and Java 21, plus Node.js with corepack enabled to install the Yarn workspaces the frontend modules need. The pinned package manager is yarn 4.9.1, and the build command is ./mvnw clean install -Ppublic.

How much does Nexus Pro cost according to sonatype/nexus-public?

The repository states no prices anywhere. It says Pro customers can contact Sonatype support, points other users to the Community Edition download, and lists the issue tracker, the Sonatype Community forum and a separate address for reporting a security vulnerability.

Can sonatype/nexus-public run on PostgreSQL under Kubernetes?

Not from this codebase. The embedded H2 database is described as appropriate for small workloads, and use of an external PostgreSQL database, which the README ties to deploying under Kubernetes, is listed as part of Community Edition.

Where do the default administrator credentials end up in sonatype/nexus-public?

The application creates a sonatype-work directory at public/selfhosted/assemblies/nexus-repository-core/target/sonatype-work, and that directory contains the default administrator credentials, the database and the file blobstore.

Does sonatype/nexus-public include npm, Docker or PyPI format support?

Not in the Core codebase, which covers maven, raw and APT. npm, Docker, NuGet, PyPI and many other formats are listed as additional support in the Community Edition binary.

Official sources

  1. License: EPL-1.0
  2. Project website
  3. README
  4. Releases
  5. sonatype/nexus-public on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/sonatype-nexus-public.svg)](https://hysenlabs.com/projects/sonatype-nexus-public)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/sonatype-nexus-public.svg)](https://hysenlabs.com/projects/sonatype-nexus-public)

Was this useful?