Verified75% confidenceFactExact time
The commit is signed with GPG key ID B5690EEEBB952194 and has been verified.
3
Sources
75%
Confidence
Long-term
Relevance
10/12/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedSigning published packages with GPG keys allows users to verify that the version was genuinely produced by a legitimate build process, thereby reducing the risk of dependency poisoning attacks.74% similarVerifiedGPG signing is a digital signature mechanism based on asymmetric encryption; in GitHub's release workflow, maintainers use a private key to sign release artifacts, and users can verify the signature's validity using a public key.71% similarUnverifiedGNAP requires the client to prove possession of the corresponding private key (typically Ed25519) via HTTP message signatures on every request, and the resource server only needs to complete signature verification locally without any database query or network call.67% similarVerifiedIn the embedded token scenario, the server signs the token with a private key, and the Databricks platform uses the corresponding public key to verify the signature's integrity.64% similarUnverifiedFor signature-based verifiable claims (such as JWTs signed with a private key), the recipient can verify the signature but cannot confirm the true ownership of the key.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1006558API
curl https://kongchang.com/api/v1/knowledge/claims/1006558MCP
get_claim(id=1006558)