openwright-langfuse
A Langfuse forwarder for OpenWright: keep your traces in Langfuse and attach the OpenWright verdicts back to them.
- forward — co-ingest a telemetry batch to Langfuse unchanged (Basic auth +
x-langfuse-ingestion-version: 4). - backlink — push
openwright:<control>scores (the verdicts) onto the trace, with the reason as a comment; returns a deep-link. - pull — read Langfuse scores/evals back as
ComplianceEvents (evals-as-evidence).
from openwright.connectors import load
fwd = load("openwright.forwarders", "langfuse")
cfg = {"host": "https://cloud.langfuse.com", "public_key": "pk-…", "secret_key": "sk-…", "trace_id": trace_id}
fwd.backlink(report, config=cfg) # openwright:* verdicts now on the Langfuse trace
No partnership or endorsement implied; built on Langfuse's public HTTP API. No crypto is reimplemented here.
Metadata
Release files for openwright-langfuse 0.4.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 |
|---|---|---|---|---|
| openwright_langfuse-0.4.0.tar.gz | 3.6 kB | With provenance | Details for openwright_langfuse-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openwright_langfuse-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for openwright_langfuse-0.4.0-py3-none-any.whl |
Total release size: 7.3 kB
Release files / openwright_langfuse-0.4.0.tar.gz
| Download URL | openwright_langfuse-0.4.0.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b71ed05ef6fe4b9d40360a514295a2b625aa2ef035c59eb5bc99c49cd47eeac9
|
|
BLAKE2b-256 checksum How to use checksums |
a09025e582ff340c2cd669ee5c5bfbf6c6ea05b26812feafbd963f782b2d8446
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 4, 2026.
Transparency logRelease files / openwright_langfuse-0.4.0-py3-none-any.whl
| Download URL | openwright_langfuse-0.4.0-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3dedb09233f05dceb06245e73a29498afcd851806c4003c79da00a0a7c6e4f76
|
|
BLAKE2b-256 checksum How to use checksums |
1f1178307135f3ed21972e464be5e5c3f2644206239e8db118bbbafd725b8bc6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 4, 2026.
Transparency logSecurity for openwright-langfuse 0.4.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 openwright_langfuse-0.4.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 Jun 4, 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.