google/trillian

A transparent, highly scalable and cryptographically verifiable data store.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 18th, 2026
Created on May 12th, 2016
Open Issues & Pull Requests: 47 (+0)
GitHub issues: Enabled
Number of forks: 466
Total Stargazers: 3,752 (+0)
Total Subscribers: 75 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.3 hours
Mean response time: 3.6 days
90th percentile: 7.8 days
Tracked items: 29

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,437 days
Stale 30+ days: 11
Stale 90+ days: 8

Recent activity

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

Top labels

  • Low Priority (4)
  • feature (3)
  • cleanup (2)
  • bug (1)
  • docs (1)
  • enhancement (1)
  • help wanted (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Trillian is a transparent, cryptographically verifiable data store that implements a scalable Merkle tree architecture for append-only logs.

Trillian solves the problem of building large-scale, auditable data structures where clients can cryptographically verify that data has not been tampered with or selectively hidden. It implements a Merkle tree whose contents are served from a data storage layer, enabling scalability to extremely large trees. The core system provides an append-only Log mode that fills the Merkle tree densely from the left, analogous to Certificate Transparency logs. Applications build on top of Trillian's transparent data store by providing their own personalities, which are application-specific layers that define how the underlying transparency infrastructure is used.

Trillian is production-ready and deployed by multiple organizations at scale, particularly as the foundation for Certificate Transparency log operators. The codebase is stable and no new features are planned for this version. However, the project is in maintenance mode, and the README recommends that new log operators first evaluate Tessera, which implements the next generation of transparency logs using Tiled APIs. Trillian remains suitable for organizations operating existing transparency infrastructure or those specifically requiring its Merkle tree architecture. Building and running Trillian requires Go and either MySQL or MariaDB for the data storage layer.

Development activity on the project is minimal, with the maintainers explicitly stating they do not plan to add new features and will attempt to avoid incompatible changes, though they cannot guarantee this. Community contributions are still accepted, but contributors are encouraged to file issues and discuss proposals before beginning work. The codebase is stable enough for production use but is not actively evolving with new capabilities.