Project Summary
A transparent and secure way to look up public keys.
Key Transparency provides a lookup service for generic records and a public, tamper-proof audit log of all record changes. While being publicly auditable, individual records are only revealed in response to queries for specific IDs.
Key Transparency can be used as a public key discovery service to authenticate users and provides a mechanism to keep the service accountable. It can be used by account owners to reliably see what keys have been associated with their account, and it can be used by senders to see how long an account has been active and stable before trusting it.
In a Nutshell, Google Key Transparency...
- ...
- ...
- ...
-
...
took an estimated 6 years of effort (COCOMO model)
starting with its first commit in May, 2015
ending with its most recent commit over 5 years ago
Quick Reference
Apache License 2.0
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Sub-License
Private Use
Use Patent Claims
Forbidden
Hold Liable
Use Trademarks
Required
Include Copyright
State Changes
Include License
Include Notice
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Vulnerability Exposure Index
Did You Know...
-
...
55% of companies leverage OSS for production infrastructure
-
...
data presented on the Open Hub is available through our API
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
anyone with an Open Hub account can update a project's tags
30 Day SummaryMar 1 2026 — Mar 31 2026
|
12 Month SummaryMar 31 2025 — Mar 31 2026
|
