IvanHunters
96758b9e3d
The index-entry `digest` field, and the gate and README claims around it, assume a published index that does not exist yet: decision 0002 in the marketplace proposal defers it, and #4981 tracks that work. The gate also never compared a recorded digest against the artifact it verified, so the field added surface without the check that would make it trustworthy. Drop it from this PR. Digest pinning still works from an explicit oci://host/org/repo@sha256:... reference and from the digest a tag resolves to; only the index-entry path is removed. The tag-based pinning and the verify-flag wording stay in the index README. Assisted-by: LLM Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>
Cozystack community package index (template)
This directory is a template for the standalone cozystack/packages-index repository. Copy its contents into that repository's root (moving github-workflows/validate.yaml to .github/workflows/validate.yaml) to stand up the community index and its publication gate.
The index is metadata only: it records where community packages live and who owns them. Artifacts stay in ordinary OCI registries; nothing is hosted here.
Layout
entries/<name>.yaml # one metadata-only entry per package
scripts/validate-entry.sh # offline gate: cozypkg validate + mandatory cosign
github-workflows/validate.yaml # CI that runs the gate on every entry change
Entry format
Each file under entries/ is a single record (see entries/example.foo.yaml):
name: foo.bar
ociRef: oci://ghcr.io/foo/bar
version: v1.2.3
description: A SQL database operator
maintainer: Foo <foo@example.com>
homepage: https://example.com/foo
tags:
- database
- sql
signing:
identity: https://github.com/foo/bar/.github/workflows/release.yaml@refs/heads/main
issuer: https://token.actions.githubusercontent.com
Two-lane merge policy
Following krew-index, submissions take one of two lanes:
- Owner version bump. A change that only updates an existing entry's
versionor description, leavingociRefandsigninguntouched, auto-merges once the new artifact validates and is signed by the entry's recorded cosign identity. This keeps the routine "new release of a listed package" path fast. - New entry, or a change to
ociRef,maintainer, orsigning. These are the security-relevant edits and require maintainer review before merge.
Cosign verification is mandatory on the gate for both lanes: the trust anchor is the recorded signing identity, so a bump fails if the new artifact is not signed by the originally approved identity.
Trust model
Signature verification happens here, at publication time, not at tap time. cozypkg tap and the dashboard connect flow validate an artifact's structure; they do not verify a cosign signature unless asked (with --certificate-identity / --certificate-oidc-issuer, which set a Flux pull-time verify policy). A cluster that taps a listed repository otherwise trusts that this index already verified it. The verification point is this CI gate, which pins each release to the entry's recorded identity. Independently of signing, a tapped repository is pinned to a digest and does not follow a moved tag: a tag-only tap is pinned to the digest it first resolves to. Installing an app from a tapped repository runs its charts in the management cluster, so operators should tap only sources they trust or that appear in a curated index like this one.