Package Quality
The registry separates publish validation from metadata signals. A package is not called verified because it has a description or a star count. Those fields tell you what information is available; validation checks whether the package can be identified, inspected, and consumed reproducibly.
Publish requirements
rr pkg publish validates the identity and source manifest before a package
can enter the registry.
| Field | Requirement |
|---|---|
name | Package name, unique within the namespace. |
namespace | Publisher or organization handle. |
version | Semver version matching the Git tag being published. |
license | SPDX identifier or accepted SPDX expression. |
hdl.files | Non-empty paths to the HDL files shipped by the package. |
The package should also include a one-line description, a public source URL,
and the language/library information needed to understand how the files are
compiled. Missing recommended metadata is visible in the registry instead of
being silently filled with generated text.
Versioning
Published versions use MAJOR.MINOR.PATCH semver, with an optional prerelease
suffix. Use a major version for breaking interface or behavior changes, a
minor version for backwards-compatible functionality, and a patch version for
backwards-compatible fixes.
Dependencies may use an exact version, a caret range such as ^1.2.0, or a
tilde range such as ~1.2.0. A project lock file records the resolved result
used by a build.
Do not reuse a published version for different source contents. Publish a new version and tag the corresponding source commit instead.
Registry signals
The browse page reports factual metadata signals for each package:
- source — link to the upstream repository;
- tags — searchable discovery terms;
- license — declared license and its broad classification;
- description — publisher-provided summary;
- multiple versions — more than one published version;
- last updated — the latest catalog timestamp when available.
These signals describe completeness, not correctness or independent review. Verification badges are separate and require evidence from the relevant verification process.
Before publishing
rr ip init rr pkg publish --namespace <namespace> rr pkg info <namespace>/<name>
Check the generated manifest, license, version tag, source URL, and HDL file
paths before publishing. For a package already installed in a project, use
rr pkg verify to compare its files with the recorded package data.
See the IP Manifest Reference for the
complete ip.yml schema.