opencontainers/go-digest

Common digest package used across the container ecosystem

Hosted by Linux Foundation

View on GitHub ↗Jump to charts ↓

opencontainers/go-digest has 200+ stars and 70+ forks on GitHub, is written in Go, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 60 minutes ago
Added to GitGenius on October 15th, 2026
Created on December 16th, 2016
Open Issues & Pull Requests: 11 (+0)
GitHub issues: Enabled
Number of forks: 70
Total Stargazers: 224 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.2 hours
Mean response time: 84.6 days
90th percentile: 396.4 days
Tracked items: 5

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,162 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

go-digest is a Go package that provides standardized digest and hash handling for the container ecosystem.

The package solves the problem of creating verifiable content identifiers for use in content-addressable storage systems. It allows disparate applications to agree on a unique identifier for any byte sequence without requiring mutual trust. The approach centers on computing cryptographic hashes and providing verification mechanisms through a Verifier type that works with io.Reader interfaces, enabling safe content distribution systems built on Merkle DAGs.

Developers should adopt this package when building container tools or applications that need to verify content integrity and create content-addressable identifiers. It suits any project within the container ecosystem that requires standardized digest handling. The package deals exclusively with hex-encoded digests rather than alternative encodings like base64. When accepting untrusted input, callers must validate digests using the Parse function or Validate method to ensure correctness throughout the application.

The project is considered fairly complete and battle-hardened through extensive production deployments. New feature additions are approached with skepticism, and contributors are expected to clearly describe problems and document alternatives before proposing changes. The Go API is declared stable.