Extract pinned Sigstore trusted root bytes to a zero-dependency module

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
go
Domain
backend

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-tuf v0.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:

  1. Separate Go submodule within this repo (e.g.,
    grc-store-clientkit/trustroot as its own go.mod) -- avoids the
    transitive closure of the parent module
  2. Move to go-gemara -- consumers already depend on go-gemara,
    so adding pinned root bytes there has zero incremental dependency cost
  3. New lightweight module (e.g., grc-store-protocol or 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 trustroot package
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gemaraproj/grc-store-clientkit

All issues in gemaraproj/grc-store-clientkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.