Cairn

Cryptographic audit logging for agent actions

NousResearch/hermes-agent · cluster 487 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

4open issues
0open PRs
9items grouped
Known?
Yes. 9 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 4 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
4 issues and 0 PRs.

These issues and pull requests propose structured, tamper-evident audit logging for agent actions, combining approaches such as hash-chaining, Ed25519 signatures, JSONL/SQLite storage, and CLI tooling to create verifiable records of tool calls and skill executions.

Open issues4

  • Issue#1155feat: Agent audit log — full history of actions taken
  • Issue#5041Feature: Cryptographic audit trail for tool calls and skill execution via MCP
  • Issue#9577[Feature]: Sift governance plugin — Ed25519-signed receipts for agent actions
  • Issue#11692Receipts for self-improving agents: proving which skill version produced which output

Open PRs0

No open pull requests.

4 PRs closed without merging

From the close comments: done elsewhere 1 · other 3

  • #1313 feat: agent audit log — full history of actions taken · other
  • #1819 feat(audit): structured JSONL + SQLite audit log (closes #1155) · done elsewhere
  • #1944 feat: structured audit log system — full agent action trail with CLI, problem detection, and self-query · other → #1819
  • #13082 feat(plugins): add signet — cryptographic audit trail plugin (fixes #487) · other
Closed issues · 1
  • Closed#487Feature: Cryptographic Audit Trail — SHA-256 Hash-Chained Action Log for Tamper-Proof Agent Accountability (inspired by OpenFang)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.19: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
1
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/487.json
cluster/487.md