DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check a run file offline against a key you pinned with Tracekit

Verify a .tkb run file with only the verifier and a public key, and see a tampered copy fail.

Who it is forAn auditor or security reviewer who receives a run file from a team and needs to check it without trusting that team's tools.

The problemA log handed over as a plain file gives no proof it was not edited after the fact.

The outcomeYou get exit 0 for the intact sample run and exit 1 for the tampered copy, using only the signer's public key.

What you need first

  • Python 3.9 to 3.13 (framework integrations need 3.10 or newer), or uv for the one-line demo
  • A terminal on your own machine; runs on your own machines per the README
  • Dev mode runs as your user, so it protects nothing against an agent running as you

Steps

  1. Clone https://github.com/Cygnux-Labs/Tracekit and change into the checkout.
  2. Run pip install --no-deps tracekit-ai.
  3. Run tracekit verify docs/sample/demo-run.tkb --key docs/sample/signer.pub and expect exit 0.
  4. Run tracekit verify docs/sample/demo-run-tampered.tkb --key docs/sample/signer.pub and expect exit 1.

Prompt for your agent

In the Cygnux-Labs/Tracekit checkout at <repo-path>, run `pip install --no-deps tracekit-ai`, then `tracekit verify docs/sample/demo-run.tkb --key docs/sample/signer.pub` and the same command on docs/sample/demo-run-tampered.tkb. Expect exit 0 for the intact file and exit 1 for the tampered file. Verify that the tampered file's failure points to a specific record.

Caveat. A verified run proves the record is intact, not that the agent's intent was good or that every action was captured.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page