stacklok / stacklok/toolhive-registry-server
As a platform admin, I want to use an OCI image as a registry source, so that I can support disconnected environments
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 27
- Forks
- 15
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 16
Description
A SourceHandler implementation based on OCI image to support disconnected environments. Define the specifications of the OCI image storing the registry document and address the following use cases.
- The consumer must know where the registry document is located
- The consumer must verify the image format using metadata
- The consumer may use OCI labels for metadata and discoverability
- The consumer may verify the integrity using a verifiable signature
- The producer must have a validated, configurable procedure to generate the image from its own artifact
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the SourceHandler entry point and any existing source implementations, then define the OCI image specification for the registry document. Done means the consumer and producer use cases in the checklist are specified, including discovery, metadata validation, optional labels, signature verification, and a validated configurable generation procedure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100