Unverified50% confidenceFactExact time
When 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/20/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedGit supports cryptographic signing of commits and tags using GPG, and the signature binds the commit content to the signer's private key.77% similarUnverifiedGitHub automatically attaches a verified signature to commits created through its web interface or specific integrations, and displays a 'Verified' badge in the interface.76% similarUnverifiedGitHub attestation allows users to verify, through commands such as gh attestation verify, that a certain npm package was indeed built from the specified repository and commit.74% similarUnverifiedThis change was introduced by commit 7f803af and released via GitHub's verified signature mechanism.73% similarVerifiedThe git commit mechanism does not store differences but instead takes a snapshot of the entire project state73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1074366API
curl https://kongchang.com/api/v1/knowledge/claims/1074366MCP
get_claim(id=1074366)