sigstore/rekor

Software Supply Chain Transparency Log

Hosted by Open Source Security Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

sigstore/rekor has 1k+ stars and 200+ forks on GitHub, is written in Go, and was last pushed on Oct 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 37 minutes ago
Added to GitGenius on October 15th, 2026
Created on June 17th, 2020
Open Issues & Pull Requests: 73 (+0)
GitHub issues: Enabled
Number of forks: 226
Total Stargazers: 1,218 (+0)
Total Subscribers: 17 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.6 hours
Mean response time: 66.4 days
90th percentile: 286.1 days
Tracked items: 49

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 763 days
Stale 30+ days: 17
Stale 90+ days: 15

Recent activity

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

Top labels

  • enhancement (25)
  • bug (15)
  • rekor-v2 (11)
  • question (4)
  • api (1)
  • pathfinding (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Rekor is a transparency log that provides an immutable, tamper-resistant ledger for recording and verifying metadata generated throughout a software project's supply chain.

Rekor addresses the need for verifiable, non-repudiable records of software artifacts and their provenance. It works by accepting signed metadata submissions through a REST API, storing them in an immutable transparency log, and allowing any party to query the log to verify inclusion proofs and check the integrity of recorded entries. This enables software maintainers and build systems to create auditable records of their supply chain activities, while consumers can verify the authenticity and lifecycle of artifacts they depend on.

Rekor is suitable for organizations that need to demonstrate supply chain transparency and integrity, particularly those building or distributing software at scale. It works well as a standalone service but is designed as part of sigstore's broader software signing infrastructure. The project supports extensibility for different manifest schemas and PKI tooling, making it adaptable to various workflows. A public instance is available with a 99.5% availability SLO and 24/7 operational support, though it enforces a 100KB attestation size limit; organizations with larger requirements can run their own instance.

The project is in a transitional phase, with the current v1 maintained in stable mode while active development focuses on a new architecture. The upcoming v2 redesign uses tile-based logs and a modernized version of Trillian to improve operational efficiency and reduce maintenance burden. The codebase is written in Go and documented through official sigstore documentation, with the v1 API following semantic versioning to ensure stability for production workloads.