Unverified50% confidenceFactExact time
After the software tests passed, GitHub produced an official release, but the development repository is private, so external users cannot download the release attachments.
1
Sources
50%
Confidence
Long-term
Relevance
10/24/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe accessibility of GitHub Release attachments inherits the repository's visibility settings: if the repository is private, unauthorized users cannot download the attachments.76% similarUnverifiedAIClaw's checksum comparison only verifies that the downloaded file matches the digest provided by the release; it does not independently prove the publisher's identity, and the real trust anchor is the release channel (the GitHub Release page) itself.67% similarUnverifiedThe project author states in the README that EXE and DLL files are never released, and that any copy containing such files is not an official version; install only from the GitHub repository or npm.67% similarUnverifiedCAI Tools' GitHub repository states that 'the code here is not the latest', and the repository is only used for submitting bugs, so that source code cannot be used to audit the actually installed build artifacts.67% similarUnverifiedIf the target repository is a private repository, failing to complete GitHub authorization will cause creation of the cloud environment to fail because the code cannot be pulled.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1094596API
curl https://kongchang.com/api/v1/knowledge/claims/1094596MCP
get_claim(id=1094596)