# transparency log Published articles for transparency log. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Inspecting the Source of Go Modules DevFeed: [Inspecting the Source of Go Modules]() Original publisher: [Read original article]() Author: Filippo Valsorda Published: 2026-02-12T13:48:03Z Content type: article Language: en Sources: [Filippo Valsorda]() Topics: [Go Language](), [modules](), [integrity](), [Security](), [GitHub](), [Code]() Tags: [cryptographic](), [github](), [go](), [integrity](), [modules](), [security](), [tooling](), [transparency-log](), [verification](), [verify]() ### AI overview The article explains how the Go Checksum Database verifies module source and helps protect against altered tags and targeted versions. It argues that viewing code directly on GitHub can bypass this verification, using a malicious BoltDB module incident as an example, and recommends fetching source with Go tooling for review. ### Source excerpt Code hosts like GitHub don't necessarily show the correct source of Go modules. pkg.geomys.dev is a new convenient viewer for module source. ## Building a Transparent Keyserver DevFeed: [Building a Transparent Keyserver]() Original publisher: [Read original article]() Author: Filippo Valsorda Published: 2025-12-19T14:03:18Z Content type: tutorial Language: en Sources: [Filippo Valsorda]() Topics: [systems](), [rate-limiting](), [Go Language](), [Server](), [SQLite](), [Authentication](), [Tooling](), [Command-line interface]() Tags: [api](), [authentication](), [building](), [cli](), [go](), [privacy](), [rate-limiting](), [server](), [sqlite](), [tooling](), [transparency-log]() ### AI overview This tutorial builds a centralized keyserver for looking up age public keys. It applies transparency-log technology to help keep the operator accountable and prevent surreptitious injection of malicious keys while protecting user privacy. The implementation uses a Go server, SQLite database, APIs, email authentication, a CAPTCHA, and a Go CLI. ### Source excerpt We apply a transparency log to a centralized keyserver step-by-step, in less than 500 lines, with privacy protections, anti-poisoning, and witness cosigning. ## Signing container images: Comparing Sigstore, Notary, and Docker Content Trust DevFeed: [Signing container images: Comparing Sigstore, Notary, and Docker Content Trust]() Original publisher: [Read original article]() Author: Hrittik Roy Published: 2023-09-26T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Containers](), [supply-chain-security](), [Security](), [Docker]() Tags: [article](), [awareness](), [blog](), [container-images](), [container-security](), [cryptographic](), [developer](), [devops](), [docker](), [draftdotdev](), [kubernetes](), [oidc](), [openid-connect](), [security](), [signing](), [sigstore](), [snyk-container](), [software-supply-chain](), [transparency-log](), [tutorial]() ### AI overview This article compares Sigstore Cosign, Notary v2, and Docker Content Trust for signing and verifying container images. It explains how cryptographic signatures help establish image authenticity, integrity, ownership, accountability, and supply-chain compliance, then introduces a tutorial for integrating one of the tools into a workflow. ### Source excerpt In this article, we will compare three popular container signing solutions: Sigstore Cosign, Notary v2, and Docker Content Trust (DCT), (a.k.a. Notary v1). You'll learn about their features, capabilities, and suitability for securing container image supply chains. ## New Chainguard Academy tutorial: Cosign the manual way DevFeed: [New Chainguard Academy tutorial: Cosign the manual way]() Original publisher: [Read original article]() Published: 2023-03-30T00:00:00Z Content type: tutorial Language: en Sources: [Chainguard: Unchained]() Topics: [Tutorial](), [sigstore](), [Security](), [supply-chain-security](), [Command-line interface](), [Software]() Tags: [algorithm](), [chainguard](), [chainguard-academy](), [cli](), [cosign](), [rekor](), [rsa](), [security](), [sha-256](), [signing](), [sigstore](), [software-artifact-signing](), [transparency-log](), [trust](), [tutorial](), [verify]() ### AI overview This article introduces a Chainguard Academy tutorial that explains Cosign's blob-signing capabilities. It covers generating an RSA key pair, signing data with SHA-256, uploading signatures to the Rekor transparency log, and verifying the signature. ### Source excerpt New Chainguard Academy tutorial unpacks Cosign the manual way and explores Cosign's blob signing capabilities. ## Chainguard contributes Rekor Search project to Sigstore DevFeed: [Chainguard contributes Rekor Search project to Sigstore]() Original publisher: [Read original article]() Published: 2023-03-24T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [browser](), [Code](), [Git]() Tags: [browser](), [chainguard](), [git](), [gitsign](), [hash](), [index](), [open-source-software](), [rekor](), [search](), [sigstore](), [transparency-log](), [ui]() ### AI overview Chainguard is donating its open-source Rekor Search UI project to Sigstore. The browser-based search engine lets users search and sort entries in the public Rekor transparency log by email, hash, entry UUID, or log index, with support for Gitsign signatures and Git commit associations. ### Source excerpt Chainguard announces its donating the Rekor Search UI project to Sigstore, allowing users to conveniently search entries in the public Rekor transparency log.