Unverified50% confidenceFactExact time
GitHub hosts the public keys uploaded by users and marks them as Verified or Unverified on commit and tag pages.
1
Sources
50%
Confidence
Long-term
Relevance
10/28/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen verifying a commit signature, GitHub compares the signature in the commit with the public key bound to the committer's account, and only shows Verified if the two match; this mechanism guarantees that the commit comes from that account, not that the code content is correct.79% similarVerifiedGitHub automatically attaches a verified signature to commits created through its web interface or specific integrations, and displays a 'Verified' badge in the interface.77% similarVerifiedGit supports cryptographic signing of commits and tags using GPG, and the signature binds the commit content to the signer's private key.77% similarUnverifiedThe GitHub REST API endpoint GET /repos/{owner}/{repo}/git/tags/{tag_sha} can return tag object details, and the response for a signed tag includes a verification field, where verified being true indicates the signature is valid.76% similarUnverifiedGitHub's trust system is built on sustained genuine contributions rather than registration time; accounts without actual code commits, issue discussions, and pull request records are identified as anomalous by risk-control models.75% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1108146API
curl https://kongchang.com/api/v1/knowledge/claims/1108146MCP
get_claim(id=1108146)