Extract pinned Sigstore trusted root bytes to a zero-dependency module
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start with the clientkit trustroot package and inspect the module dependency graph. Compare the separate submodule, go-gemara, and lightweight-module options against complyctl#854. Done means consumers can import the pinned trusted root bytes without pulling the publishing infrastructure dependencies.
Written by the indexing model from the issue text.
Description
Context
While assessing grc-store-clientkit adoption for bundle consumption in
complyctl (complytime/complyctl#854), we identified that the trustroot
package contains a valuable shared asset -- pinned public-good Sigstore
trusted root bytes -- but importing it carries a disproportionate
transitive dependency cost.
Problem
Importing any clientkit package (including trustroot) pulls ~13 new
transitive dependencies into the consumer, including:
- Cloud KMS SDKs:
cloud.google.com/go/kms,Azure/azure-sdk-for-go
(azcore + azidentity),aws/aws-sdk-go-v2(core + config + credentials +
kms) -- 8 packages total - Hub protocol:
revanite-io/grc-store-protocol - Auth/identity:
coreos/go-oidc/v3 - Crypto/signing:
go.step.sm/crypto,sassoftware/relic,
theupdateframework/go-tufv0.7.0
Go's module system imports at the module level, so even a single-package
import pulls the full transitive closure. For consumers that only need the
pinned trust root JSON blob (e.g., for Sigstore verification of OCI
artifacts), this dependency cost is prohibitive.
Proposed Solution
Extract the pinned Sigstore trusted root bytes to a zero-dependency or
minimal-dependency location. Options:
- Separate Go submodule within this repo (e.g.,
grc-store-clientkit/trustrootas its owngo.mod) -- avoids the
transitive closure of the parent module - Move to
go-gemara-- consumers already depend ongo-gemara,
so adding pinned root bytes there has zero incremental dependency cost - New lightweight module (e.g.,
grc-store-protocolor similar) --
designed for zero-dependency shared constants and wire contracts
Benefit
Enables downstream consumers (e.g., complyctl) to adopt a shared, curated
trust root without importing publishing infrastructure they don't use.
Related
- complytime/complyctl#854 (spike assessment, sections 6 and 9)
- clientkit
trustrootpackage
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 45m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from gemaraproj/grc-store-clientkit
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
good first issue help wanted
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Stale
Difficulty 5/5 Over a week Newbie friendliness 25/100
gemaraproj/grc-store-clientkit#2 · 1 comment ·
-
Standardize Artifact Packaging and Distribution via OCIMay be free again @sonupreetam claimed this 212 days ago, and no pull request is open. Openenhancement Stale
gemaraproj/grc-store-clientkit#1 · 2 comments · 2 reactions · 2 assignees ·
All issues in gemaraproj/grc-store-clientkit
Similar issues
-
Pin and verify Security Insights schema in lintinsights targetPossibly taken @imshubham22apr-gif claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gemaraproj/gemara#618 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
a2aproject/a2a-go#597 ·
Maintainers usually reply within 1 day
-
scopes: GetAllowedTopics, GetProtectedTopics, and GetScopedTopics include empty topic names and do not trim whitespace charactersPossibly taken @patelshivani2283-lab claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area/networking kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
siderolabs/talos#14972 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day