Checking a commit
Prove offline that a commit on main passed, and the API the keys come from.
Check a commit
Anyone can check, offline, that a commit on main was proven. Save land's public keys once, fetch the signatures that came with the result, and verify.
curl -fsS https://api.useland.dev/v1/land/keys -o land-keys.json git fetch origin refs/land/attestations:refs/land/attestations land verify HEAD --pubkey land-keys.json --protected main
It exits 0 when the commit's exact files passed, and 1 with the reason when they did not.
What it proves
The signature covers the exact tree of files, so a commit that was amended, rebased or edited after the verdict fails the check. The signatures travel with your repository in refs/land/attestations, which is why every push sends that ref together with the commit.
The API
The keys come from land's API, described in openapi.json. The API is versioned in its address (/v1). A breaking change gets a new version, and the old one keeps working for at least 90 days after its removal is announced in these docs.