Manage packages and versions

Browse package contents

1. Open a repository.
2. Select its PyPI, npm, or Maven tab.
3. Select a package.
4. Select a version to inspect its artifacts and metadata.

Packages belong to one ecosystem. Browser downloads use temporary links; package managers use the repository URL and a token.

Browse Container and Helm content

Select OCI, optionally filter Content type to Container OCI or Helm OCI, then browse:

OCI repository path → tags and immutable digests → manifest/index → configs, layers, and referrers

Tags are mutable references, not versions. Manifest digests are immutable identities. A multi-platform image index can point to several platform manifests, and an attachment points back to its subject through the OCI referrers graph.

Use the typed tag or manifest actions shown by Ravenstash. Removing a tag does not necessarily remove its manifest or shared blobs; unreferenced content follows the OCI garbage-collection lifecycle.

Package actions

Action	Effect
Yank version	Discourages normal resolver selection without deleting files. Exact-version behavior depends on the client.
Delete version	Moves the version to the repository trash. It stops being installable at once. Existing client caches are unaffected.
Delete package	Moves every version of the package to the trash.

In an organization, these actions need the Maintainer or Admin role on the repository. Publishing a version, pushing an image, or adding a container image tag needs Publisher; removing a container image tag needs Maintainer, because the untagged manifest can then be cleaned up. See Roles and grants.

Trash

Deleting never removes content immediately. A deleted package version, a deleted PyPI or Maven file, or a deleted container image or Helm chart manifest goes to the repository trash and is permanently deleted after seven days. Removing a container image tag is immediate and does not use the trash.

While content is in the trash:

• it cannot be installed, pulled, or downloaded, and it no longer appears in the repository contents;
• its version number, filename, or manifest digest stays reserved, so publishing the same version again is refused until the permanent deletion date, which the refusal shows. Other versions of the package can still be published; and
• it still counts toward your stored-package usage.

To restore content, open the repository, select Trash, and choose Restore on the item, or Restore all for every trashed item of one package or image path. Each item shows when it will be permanently deleted. Restored content is installable again and returns with its current Package Protection state, because checks keep running on content in the trash.

Everyone who can read the repository can see its trash. In an organization, restoring needs the Maintainer or Admin role on the repository, the same roles that can delete.

Cached upstream packages

Deleting cached upstream content does not block it. A later eligible request may fetch it again.

Content security

Ravenstash Protection helps you assess PyPI, npm, and Maven package versions for malware, known vulnerabilities, and other security risks. Confirmed malicious packages are blocked, and findings remain visible with the affected version and files. Learn how to interpret statuses, reviews, protection policies, quarantine, and repository blocks in Package Protection.

Container and Helm attachments such as signatures, attestations, SBOMs, and provenance remain discoverable alongside their subject. Keep the verification controls required by your deployment policy.

Within OCI, use Content type to choose All OCI, Container OCI, or Helm OCI. The filter applies across all results and works with search. Container images and charts have distinct labels and icons; attachments remain linked to their subject digest. A subject that has not been published is shown as unresolved.