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:
- Record the agent's intent before the work runs (an activity, a step) as an action under a contract:
POST /v1/actionswith the contract, subject and parameters taken from the call's own arguments. The result of the work is never sent. - 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 ./sdk/python ./integrations/python[temporal,inngest] # from this repository
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.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| commitlayer_integrations-0.1.0.tar.gz | 33.7 kB | With provenance | Details for commitlayer_integrations-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| commitlayer_integrations-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for commitlayer_integrations-0.1.0-py3-none-any.whl |
Total release size: 62.3 kB
Release files / commitlayer_integrations-0.1.0.tar.gz
| Download URL | commitlayer_integrations-0.1.0.tar.gz |
|---|---|
| Size | 33.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcdb3a7ff4049cfb9e1177d4ff1a6c2e49a5689983eb6cbfa08e44a68cc56f5b
|
|
BLAKE2b-256 checksum How to use checksums |
fe0687dcb0b19b98959f919d65d195458407fe029f37432d2fe0ca2bdb3d7ebd
|
| 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 logRelease files / commitlayer_integrations-0.1.0-py3-none-any.whl
| Download URL | commitlayer_integrations-0.1.0-py3-none-any.whl |
|---|---|
| Size | 28.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
55fe8f95e98be3ae38ce679df41e3c8b71ee0df885e45a4d1be38aae4f9062cb
|
|
BLAKE2b-256 checksum How to use checksums |
0a54fbf9f6a8dc0b87094b510225a08a533d2352872a0289bb78be49fe98a569
|
| 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 logSecurity for commitlayer-integrations 0.1.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for commitlayer_integrations-0.1.0.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 logA 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.