Skip to main content
Change of provenance

The repository or configuration that created this release differ from a previous release. View details.

commitlayer-integrations (Python)

CommitLayer for agent frameworks and durable-workflow runtimes. One distribution, six optional packages, built on the commitlayer SDK:

Package Framework or runtime Install
commitlayer_langgraph LangGraph, LangChain v1 agents pip install 'commitlayer-integrations[langgraph]'
commitlayer_crewai CrewAI pip install 'commitlayer-integrations[crewai]'
commitlayer_openai_agents OpenAI Agents SDK pip install 'commitlayer-integrations[openai-agents]'
commitlayer_pydantic_ai Pydantic AI pip install 'commitlayer-integrations[pydantic-ai]'
commitlayer_temporal Temporal (temporalio) pip install 'commitlayer-integrations[temporal]'
commitlayer_inngest Inngest (inngest) pip install 'commitlayer-integrations[inngest]'

The four framework packages share one mapping and one recorder (commitlayer_integrations.tools.ToolRecorder): a tool name maps to a contract, the argument that holds the subject, and the arguments that are the action's parameters, in the same shape the MCP recorder's mapping file uses. Each framework package is the hook at which that recorder runs: a wrap_tool_call wrapper for LangGraph, a before_tool_call hook for CrewAI, RunHooks for the OpenAI Agents SDK, a WrapperToolset for Pydantic AI. None of them imports its framework at module load, so the tests run without any of them installed.

Each one does the same two things in its runtime's own terms:

  1. Record the agent's intent before the work runs (an activity, a step) as an action under a contract: POST /v1/actions with the contract, subject and parameters taken from the call's own arguments. The result of the work is never sent.
  2. Gate completion on the verdict: wait for GET /v1/actions/{ref} to report a settled verification and branch on PASS / FAIL / UNKNOWN. The workflow does not tell the customer "done" until the verdict is PASS.

The workflow engine makes the process durable. CommitLayer independently verifies the result, from the systems of record, after the fact. The agent may declare its intent. It may read the verdict. It must never control the independent facts, the governing contract, or the final evidence.

Python 3.10+. Both packages import without their runtime SDK installed (the SDK is imported lazily), so a service that uses only one of them does not need the other.

pip install 'commitlayer-integrations[temporal,inngest]'
export COMMITLAYER_API_KEY=spk_...                                   # never log or print it
.venv/bin/python -m pytest integrations/python/tests -q              # no Temporal server, no Inngest dev server

Metadata

Release files for commitlayer-integrations 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Change of provenance

The repository or configuration that created these release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Source distribution (sdist)

Source distribution for commitlayer-integrations 0.1.1
File Size Uploaded Provenance Actions
commitlayer_integrations-0.1.1.tar.gz 33.6 kB With provenance Details for commitlayer_integrations-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for commitlayer-integrations 0.1.1
File Interpreter ABI Platform Actions
commitlayer_integrations-0.1.1-py3-none-any.whl Python 3 none any Details for commitlayer_integrations-0.1.1-py3-none-any.whl

Total release size: 62.1 kB

Release files / commitlayer_integrations-0.1.1.tar.gz

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL commitlayer_integrations-0.1.1.tar.gz
Size 33.6 kB
Tags Source
SHA-256 checksum
How to use checksums
3fb7e51e1e7b13952f99c5580af465258ada406fb314699e4c15c666923ce8a9
BLAKE2b-256 checksum
How to use checksums
472f1c4ab54993680aa6e188cfddf5388712317c59f565a34323d7f0f0135ee9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Release files / commitlayer_integrations-0.1.1-py3-none-any.whl

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL commitlayer_integrations-0.1.1-py3-none-any.whl
Size 28.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ca486741b8d088d3649e34d3a7c47092d8069b63e0db8c8d5523adb2ee5e93ab
BLAKE2b-256 checksum
How to use checksums
b5d76ad79bed70f4199869927094a61fa38b4797412d9b051c4ce14b353c9764
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

Security for commitlayer-integrations 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Change of provenance

The repository and configuration that created this release differ from a previous release.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Select from 2 files

Attestation for commitlayer_integrations-0.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files Change of provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page