Skip to main content
The Protect action hashes selected files locally and creates signed fingerprint records using a consumer account. File contents are not uploaded. The signature binds a fingerprint to a record; it does not establish authorship, copyright ownership, or whether a description is true.

Before you start

Use an authorized consumer bearer token from your Truthlocks Verify account. A business API key is not interchangeable with that token. Store the token in a GitHub repository secret named TRUTHLOCK_TOKEN. Do not expose it to untrusted pull requests or print it in logs. The action installs the pinned @truthlocks/protect@1.1.1 CLI with Node.js 22. Start with a manually triggered workflow and a labeled test artifact.

Quickstart

Replace artifacts/report.pdf with an existing file in your checked-out repository. For release workflows, build the artifact before running this action. Pin a reviewed full commit SHA for production workflows.

Inputs

Supported categories are code, research, design, media, dataset, ai-output, writing, digital-art, and other. Directory selection excludes .git, node_modules, and symlinks. Inputs must stay inside the workspace. Unmatched patterns and an empty selection fail.

Outputs and verification

Minting a record does not itself verify its signature. With the same original file, use the CLI to verify a current consumer record:
Replace the ID and file path. The CLI reconstructs the defined personal-record-v2 signed payload from the file hash. It exits successfully only when the verifier returns VALID with signature_verified: true. Changed bytes fail verification. An ID-only request is INCOMPLETE; it cannot establish a valid signature. Private records are excluded from the public consumer portfolio and do not have public certificate/badge pages. Do not publish their IDs or assume the visibility flag hides all verification metadata from someone who already knows an ID.

Partial failures and retries

Each file creates a separate remote record. The action stops at the first failed CLI call; earlier records can already exist. Inspect those outcomes before rerunning a batch, since a repeat may create additional records. There is no all-or-nothing batch transaction or automatic mutation retry.