receipt-evidence
PulseGate's liveness check found it on 15 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 15 Sep 2026. How this is checked
receipt-evidence is an MIT-licensed command-line tool that runs commands and produces receipts describing what they actually touched. It is intended for verification, auditability, provenance tracking, and agent-driven workflows.
Inferred · not functionally tested
Overview
5 featuresPurpose: Verifying and auditing the real files and resources affected by command execution.
Inferred · not functionally tested
Audience: developers and security-conscious automation users
Inferred · not functionally tested
Functions: Unknown
Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
receipt-evidence sits in PulseGate's CLI tools & terminal category. Inferred · not functionally tested: It focuses on verifying and auditing the real files and resources affected by command execution. Inferred · not functionally tested: It is built as an open-source project for developers and security-conscious automation users. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: receipt-evidence is available on the command line, and it can be self-hosted.
Behind receipt-evidence is MaXiMo000, and it first shipped in 2026. Development happens publicly on GitHub with 13 commits in the last 90 days. Inferred · not functionally tested: Among its 5 catalogued features are command execution, touch tracking, and evidence receipts.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Command execution
- Touch tracking
- Evidence receipts
- Verification records
- Audit provenance
Topics: Inferred · not functionally tested
Built with & integrations
- Claude Code
- commit 028b3a6ffc18 · since Sep 2026
Trust & compliance
Indexing history
5What PulseGate has recorded for this listing
- Indexed15 Sep · 02:40 UTCreceipt-evidence seen via PyPI Bulk EnumeratorSource: PyPI Bulk Enumerator · Open
Frequently asked questions about receipt-evidence
- What does receipt-evidence do?
- Inferred · not functionally tested: Receipt-evidence focuses on verifying and auditing the real files and resources affected by command execution. It is catalogued under CLI tools & terminal on PulseGate.
- Who is receipt-evidence for?
- Inferred · not functionally tested: receipt-evidence is an open-source project built for developers and security-conscious automation users.
- Is receipt-evidence free?
- Basis unknown · not verified: Yes — receipt-evidence is open source under the MIT license and free to use.
- What platforms does receipt-evidence run on?
- Basis unknown · not verified: receipt-evidence runs on the command line. It can also be self-hosted.
- Is receipt-evidence still active?
- PulseGate's liveness check found it on 15 Sep 2026. Its GitHub repository shows 13 commits in the last 90 days.
- Who makes receipt-evidence?
- receipt-evidence is developed by MaXiMo000.
- How long has receipt-evidence been around?
- receipt-evidence first shipped in 2026.
- Is receipt-evidence open source?
- Basis unknown · not verified: Yes — receipt-evidence is open source under the MIT license, developed on GitHub.
Similar projects
Closest matches by what these projects do