Packages
The package registry stores the software packages published alongside a repository and gives you a page to browse them and copy the commands that install or download each one. A single repository can hold packages of five types — Container images, npm packages, PyPI packages, Go modules, and Generic artifacts — and the registry lists them together, grouped by type. From a package's own page you read its versions or tags, copy an install command for the client you use, and, for container images, remove tags you no longer need.
Where to find it
- Package list:
gitvetrix.com/{owner}/{repo}/packages - A single package:
gitvetrix.com/{owner}/{repo}/packages/{type}/{name} - Navigation: Open a repository and select Registry in the left sidebar.
Browse the package list
The list gathers every package published to the repository, grouped into a section per type. The sections always appear in the same order — Container, npm, PyPI, Go, Generic — and a type with no packages is left out entirely.
Each row shows:
- A type badge — Container, npm, PyPI, Go, or Generic.
- The package name, which links to the package's own page.
- The version summary. For a container image this is a tag count, such as 3 tags; for every other type it is the latest published version, or a dash when none is known.
- The number of downloads and how long ago the package was last updated.
- A View button that opens the package.
When the repository has no packages, the list shows No packages with the note that no packages have been published to this repository yet.
Filter the list by type
Above the list is a row of filter chips: All, Container, npm, PyPI, Go, and Generic.
- Select a type chip to show only that type's packages.
- Select All to bring every type back.
The selected chip is highlighted, and only the sections you asked for stay on screen.
Open a package
Select a package name or its View button to open the package's own page. Every package page opens with the package name, a badge for its type, and — for the non-container types — its latest version. The page then presents an install or download block with a tab per client, a Metadata panel, and a list of the package's versions or tags. The exact contents depend on the package type, described below.
Container images
A container package page (gitvetrix.com/{owner}/{repo}/packages/container/{name}) is organized around the image's tags.
Install — a tab per registry client: docker, podman, nerdctl, and oras. Each tab shows the pull command for the latest tag with a copy button.
Metadata — a panel listing the Image reference, the number of Tags, and the Registry host.
Tags — a summary panel above the table reports Total tags, Total size, the Oldest tag, and the Latest tag. A Filter tags search box narrows the table to tags whose name contains what you type. The tags table has these columns:
- Tag — the tag name.
- Digest — the start of the image digest; hover to see the full value.
- Type — the media type.
- Size — the image size.
- Pushed — how long ago the tag was pushed.
- Pull command — the pull command for that tag, with a copy button.
- Actions — a delete button for the tag.
When an image tag carries layer or manifest detail, its Pull command cell offers a Show layers control that opens a per-layer breakdown (layer number, digest, media type, and size, plus the total layer size) and a Show manifest control that reveals the manifest JSON with a Copy manifest JSON button. Select the control again to collapse it.
If no tags have been pushed, the page shows No tags with a note that no image tags have been pushed to this container repository.
Delete an image tag
- In the tags table, select the delete button on the tag's row.
- In the Delete image tag dialog, type the tag name to confirm.
- Select Delete image tag to remove it. The manifest that the tag points to is removed and cannot be recovered.
npm packages
An npm package page (gitvetrix.com/{owner}/{repo}/packages/npm/{name}) shows the package name, the npm badge, and the latest version, followed by the package description when one is published.
Install — a tab per package manager: npm, yarn, pnpm, and bun. Each tab shows the install command with a copy button.
Metadata — a panel with Latest, Versions (the count), and, when the package provides them, License, Homepage, Repository, and Maintainers.
Versions — a table with Version, Published (how long ago), and Download, where each row offers a .tgz link. A row whose file is missing reads unavailable in place of the link.
When the package publishes a README, it is rendered under a README heading at the bottom of the page.
PyPI packages
A PyPI package page (gitvetrix.com/{owner}/{repo}/packages/pypi/{name}) shows the package name, the PyPI badge, and the latest version.
Install — a tab per tool: pip, pipx, poetry, and uv, each with the install command and a copy button.
Metadata — a panel with Latest, Versions, and, when published, License, Homepage, and Maintainers.
Versions — a table with Version, Published, Filename, and Download. Each row's Download link fetches that file; a row whose file is missing reads unavailable.
A published README appears under a README heading at the bottom of the page.
Go modules
A Go module page (gitvetrix.com/{owner}/{repo}/packages/go/{module}) shows the module path, the Go badge, and the latest version.
Usage — a tab per workflow: go get, go mod, and GOPROXY. Each tab shows the command or environment setting for consuming the module, with a copy button.
Metadata — a panel with Latest, Versions, the GOPROXY base to point the Go toolchain at, and, when published, License, Homepage, and Maintainers.
Versions — a table with Version, Published, and Downloads, where each row offers .info, .mod, and .zip links for that version.
A published README appears under a README heading at the bottom of the page.
Generic artifacts
A generic package page (gitvetrix.com/{owner}/{repo}/packages/generic/{name}) holds arbitrary files grouped by version.
Download — a tab per client: curl, wget, and PowerShell. Each tab shows a download command for the latest version with a copy button.
Metadata — a panel with Latest, Versions, and, when published, License, Homepage, and Maintainers.
Versions — a table with Version and a per-version file count. Select a version to expand its file list; each file shows its name and size and offers a Download link. Below the table, a note reminds you to replace the filename placeholder in the download command with one of the filenames listed for the version.
A published README appears under a README heading at the bottom of the page.