Unverified50% confidenceFactExact time
The release commit record carries a GitHub verified signature, indicating that the release process went through the official CI channel rather than a manual push.
1
Sources
50%
Confidence
Long-term
Relevance
10/23/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedThis release record was completed by a GitHub Actions automated workflow and carries an official GitHub verified signature (Verified).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.74% similarUnverifiedWhen 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.73% similarUnverifiedGitHub's Trusted Publishing combined with GPG signing mechanisms can prove that a given npm package was indeed published by the CI/CD pipeline of a specific repository.73% similarUnverifiedThe commit was signed by project maintainer jmorganca and released with a verified signature through GitHub.73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1090984API
curl https://kongchang.com/api/v1/knowledge/claims/1090984MCP
get_claim(id=1090984)