Skip to content
Back to the index

Traceseal

traceseal.ioInfrastructure

PulseGate's liveness check found it on 13 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 27 Jun 2026. How this is checked

Traceseal provides cryptographic proof of actions performed by AI agents, offering a tamper-evident audit trail for each invocation. It addresses the challenge of verifying what an AI agent did, who authorized it, and who attested to the execution, all without requiring access to the operator’s environment or keys. The tool is built around a receipt system that encapsulates execution details, provenance, and attestation in a single, verifiable JSON document.

Inferred · not functionally tested

Open SourceApache-2.0CLI
Traceseal preview
Visit traceseal.io

Overview

6 features

Purpose: Proving what AI agents executed and verifying their work without relying on the operator.

Inferred · not functionally tested

Audience: AI platform engineers and organizations governing agent workflows

Inferred · not functionally tested

Functions: monitoring, agents

Inferred · not functionally tested

Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: unknown

Recorded constraints: pricing: open_source · license: Apache-2.0 · platforms: CLI, WEB · deployment: cli

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: traceseal.io · github.com. These links do not verify the individual claims.

Traceseal sits in PulseGate's AI security & guardrails category. Inferred · not functionally tested: It focuses on proving what AI agents executed and verifying their work without relying on the operator. Inferred · not functionally tested: It is built as an open-source project for AI platform engineers and organizations governing agent workflows. Basis unknown · not verified: Traceseal is open source under the Apache-2.0 license. Basis unknown · not verified: It runs on the command line.

Traceseal builds and maintains Traceseal, and it first shipped in 2026. Development happens publicly on GitHub with 4 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are signed receipts, ground-truth verification, and agent replay.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Signed receipts
  • Ground-truth verification
  • Agent replay
  • Manifest validation
  • Ed25519 signatures
  • SHA-256 hashing

Topics: Inferred · not functionally tested

Tags
agent-accountabilitycryptographic-receiptsaudit-trailsagent-governance
AI capabilities
Structured
Inference: HybridWeights: Open

JSON profile · Text profile · Access guide

Built with & integrations

Written with
Claude Code
Runs on
CLI
Written with — evidence
Claude Code
commit 0cc951ee8e56 · since Apr 2026

Trust & compliance

License
Apache-2.0
Public signals
HTTPSOpen SourceFree tierGitHubActive maintenance

Indexing history

9

What PulseGate has recorded for this listing

  1. Indexed6 Oct · 08:54 UTC
    Trusted timestamps for AI agent logs: what RFC 3161 proves, and what it does not seen via DEV.to articles
    Source: DEV.to articles · Open
  2. Indexed29 Sep · 09:14 UTC
    OWASP Top 10 for Agentic Applications: what it asks you to record, and who should sign it seen via DEV.to articles
    Source: DEV.to articles · Open
  3. Indexed22 Sep · 08:55 UTC
    MCP security: what to log when an AI agent calls tools, and what the log can prove seen via DEV.to articles
    Source: DEV.to articles · Open
  4. Indexed15 Sep · 14:31 UTC
    SOC 2 for AI agents: what evidence an auditor can actually accept seen via DEV.to articles
    Source: DEV.to articles · Open
  5. Indexed1 Sep · 11:49 UTC
    The EU AI Liability Directive is dead: what actually governs AI agent harm now seen via DEV.to articles
    Source: DEV.to articles · Open
  6. Indexed25 Aug · 09:12 UTC
    Indirect prompt injection: how an AI agent gets hijacked by the data it reads seen via DEV.to articles
    Source: DEV.to articles · Open
  7. Indexed18 Aug · 08:53 UTC
    Transparency log witnesses: how cosigned checkpoints make a log tamper-evident seen via DEV.to articles
    Source: DEV.to articles · Open
  8. Indexed28 Jul · 09:26 UTC
    Signed execution receipts: a primer on why logs are not evidence seen via DEV.to articles
    Source: DEV.to articles · Open
  9. Indexed19 Jul · 10:27 UTC
    EU AI Act Article 50: what it means for teams running AI agents seen via DEV.to articles
    Source: DEV.to articles · Open

Frequently asked questions about Traceseal

What is Traceseal?
Inferred · not functionally tested: Traceseal focuses on proving what AI agents executed and verifying their work without relying on the operator. It is catalogued under AI security & guardrails on PulseGate.
Who is Traceseal for?
Inferred · not functionally tested: Traceseal is an open-source project built for AI platform engineers and organizations governing agent workflows.
Does Traceseal have a free plan?
Basis unknown · not verified: Yes — Traceseal is open source under the Apache-2.0 license and free to use.
What platforms does Traceseal run on?
Basis unknown · not verified: Traceseal runs on the command line.
Is Traceseal still maintained?
PulseGate's liveness check found it on 13 Sep 2026. Its GitHub repository shows 4 commits in the last 90 days.
Who makes Traceseal?
Traceseal is developed by Traceseal.
How long has Traceseal been around?
Traceseal first shipped in 2026.
Is Traceseal open source?
Basis unknown · not verified: Yes — Traceseal is open source under the Apache-2.0 license, developed on GitHub.

Similar projects

Closest matches by what these projects do