This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.1.2 instead.
Reason given by maintainers: Superseded by 0.1.2. The publish attestation attached to this release contains an internal source-repository reference that should not have been published in this form. No credentials or secrets are exposed. See https://pypi.org/project/langchain-alex/0.1.2/.
langchain-alex
Verify signed ALEX Evidence Packages inside LangChain and LangGraph workflows. The verifier checks the package against a public key obtained separately from the evidence bundle and fails closed on unsupported schemas, signature failures, incomplete evidence, or inconsistent declared outcomes.
valid=True means that the evidence package passed verification and carries a verified outcome.
Authentic bundles documenting failed or inconclusive runs remain rejected; inspect reason and
outcome separately.
Requirements
- Python 3.10 or newer
- OpenSSL available as
opensslonPATH
Install
pip install langchain-alex
Verify an Evidence Package
from langchain_alex import AlexEvidenceVerifier
verifier = AlexEvidenceVerifier.from_key_files("alex-public-key.pem")
result = verifier.verify_file("evidence-bundle.json")
print(result.valid, result.reason, result.outcome)
The trust anchor is intentionally supplied separately. A public key embedded only in the bundle is not trusted.
LangChain tool
tool = verifier.as_tool()
result = tool.invoke({"bundle": evidence_bundle})
The tool returns a JSON-serializable object with valid, reason, bundle_id, schema_version,
outcome, and claim_ladder.
LangGraph node
from typing_extensions import TypedDict
from langgraph.graph import END, START, StateGraph
class State(TypedDict):
evidence_bundle: dict
alex_verification: dict
graph = StateGraph(State)
graph.add_node("alex_verify", verifier.as_langgraph_node())
graph.add_edge(START, "alex_verify")
graph.add_edge("alex_verify", END)
app = graph.compile()
result = app.invoke({"evidence_bundle": evidence_bundle})
assert result["alex_verification"]["valid"] is True
The node returns a state update and does not mutate its input state. Route on both valid and
outcome when the graph controls a consequential action.
Development
python -m pip install -e ".[dev]"
python -m pytest
ruff check .
python -m build
The verifier implementation is also used by the repository's standalone Python CLI at
tools/verify-bundle/verify.py; the integration does not maintain a second verdict algorithm.
Public evidence
The public ALEX record shows a human-readable projection of a signed Evidence Package plus the verifier path and explicit limits of the claim. It is evidence of the recorded execution and controls, not proof that the underlying work is professionally correct.
Metadata
Release files for langchain-alex 0.1.1
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 |
|---|---|---|---|---|
| langchain_alex-0.1.1.tar.gz | 27.6 kB | With provenance | Details for langchain_alex-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| langchain_alex-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for langchain_alex-0.1.1-py3-none-any.whl |
Total release size: 43.8 kB
Release files / langchain_alex-0.1.1.tar.gz
| Download URL | langchain_alex-0.1.1.tar.gz |
|---|---|
| Size | 27.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17270c56ff1839a1a1d658e1f49d01045e53bd81a77db9516564239cf197b21b
|
|
BLAKE2b-256 checksum How to use checksums |
af334a35ea6993ccfc35d08e7dba5f83a62dd7bb19978e5ef810894f1ebc2dea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 2, 2026.
Transparency logRelease files / langchain_alex-0.1.1-py3-none-any.whl
| Download URL | langchain_alex-0.1.1-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac31088196fcdaf228fea360853c980c7a29bba9fd1e7066e064b8e9d4483154
|
|
BLAKE2b-256 checksum How to use checksums |
b3894ff4a2eca931e66f65a5f72be819e42fb8d43811d5b06f02bf561a24c97e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 2, 2026.
Transparency logSecurity for langchain-alex 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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for langchain_alex-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 Oct 2, 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.