A package registry is infrastructure. When it works, nobody thinks about it. When someone does open it, it’s usually because something feels off: a release didn’t show up, an install failed, or a security alert came in.

The organization overview didn’t help with that. It opened with the number of packages, repositories and members, figures that rarely change and never tell you whether anything is wrong. v0.56.0 turns the overview into a health board that leads with the problems, and refreshes the rest of the interface along the way.

A dashboard built around anomalies

The overview now answers one question first: is anything broken?

Pricore organization dashboard with a repository health summary, repository tiles showing sync status and recent sync history, a security panel and a downloads chart
The new overview puts failing syncs and vulnerabilities ahead of totals.
  • Repository health. A summary in the header counts healthy, failing and pending repositories. Below it, each repository gets a tile with its sync status and a strip showing the outcome of its last 10 syncs. Failing repositories are always listed first.
  • Security at a glance. A security panel shows how many known vulnerabilities affect the latest and development versions of your packages, broken down by severity. When there are none, it says so.
  • Totals as context. Package, repository and member counts are still there, as a single line under the organization name that links to each list. Downloads keep their chart, next to the security panel.

The same sync history strip appears on each repository page, alongside a summary of status, last sync, package count and webhook state. Repositories that have never synced get a Sync Now shortcut instead of an empty table.

Package pages you can scan

The package page opens with what you usually need: the latest version, a description, where the package comes from and whether that source synced successfully. A 30-day download sparkline sits on the right, and the composer require command is ready to copy right below.

Pricore package page with header, install command and a versions table listing advisories, archive size, commit and release date
Versions are now an aligned table with advisories, archive size, commit and release date.

Readme, Versions and Downloads are now tabs. The versions list became a table you can scan down a column: the latest release is marked, branches are easy to tell apart from tags, and advisories are colored by severity. Hover a row to copy the exact composer require command for that version, and filter by stable or development versions.

Pricore package downloads tab with total downloads, downloads in the last 30 days with trend, daily average and a chart per day
The Downloads tab shows exact numbers and the trend against the previous 30 days.

The packages list got the same treatment. Packages are grouped by vendor, show their description, source repository and latest version, and can be filtered by name.

Jump back to what you were working on

Hover over Repos or Packages in the sidebar to see the ones you opened most recently. One click takes you straight there, without going through the list first.

Pricore sidebar with a recently visited menu listing four packages next to the Packages item
Recently visited packages and repositories are one hover away.

Easier to read

Small text like badges, timestamps and README code blocks is larger and easier to read, while screens stay just as compact.

We also cleaned up the details that show up on every page. Status labels share one consistent style. Git provider icons use their brand colors. Muted backgrounds lost their beige tint for a more neutral look. Notifications got a cleaner design with a countdown bar that pauses while you hover over them.

Upgrading

This release adds a table to track recently visited repositories.

Ready to ship private packages?

Start a managed registry in minutes, or run the same open-source code on your own infrastructure.