How sigstore/sigstore-java works
Project type and purpose
• This is a multi‐module open‐source Java client ecosystem (a “monorepo”) for the Sigstore project.
• At its heart is a core library (“sigstore-java”) offering keyless signing and verification, DSSE verification, JSON canonicalization, and a TUF client.
• Around it are: CLI tools (sigstore-cli, tuf-cli), build-tool plugins (Gradle and Maven), testkit for integration tests, example apps, and fuzzing targets.
File structure
• Top-level Gradle build logic under build-logic-*
• Sample applications under examples/
• Fuzzers under fuzzing/
• Core library under sigstore-java/ (packages: cli, http, fulcio, rekor, oidc, tuf, dsse, encryption, json)
• CLI wrappers under sigstore-cli/ and tuf-cli/
• Build-tool integrations under sigstore-gradle/ and sigstore-maven-plugin/
• Test harness under sigstore-testkit/
• Sandbox experiments, scripts, CI configs, and metadata at root
README for additional insights
• Public API limited to KeylessSigner and KeylessVerifier (Java 11 minimum)
• Typical workflow: sign file → Fulcio CA (gRPC) → Rekor log (REST) → optional Timestamp (HTTP) → output a “bundle” → verify bundle against Fulcio roots, Rekor inclusion proofs, TUF metadata
• Published artifacts on Maven Central, Javadoc hosted online
Detail level
• Drill into the core library’s sub‐packages (fulcio, rekor, oidc, tuf, dsse, encryption, json).
• How the “bundle” payload travels from signer → Rekor → verifier.
• Build-logic and CI/packaging as separate lanes.