Skip to main content
Yanked

This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 1.0.1 instead.

laidline-vllm

vLLM Model Runner V2 logits processor for the Laidline text watermark (SynthID or KGW), plus an ack-header middleware. It is the only marking that has to live outside the sidecar.

  • Install it into vLLM's environment (it pulls in laidline[text]). The entry point vllm.logits_processors: laidline loads LaidlineTextWatermark with no flag needed; only requests that opt in are marked.
  • LAIDLINE_CONFIG names the Laidline config. The processor reads watermark.text from it. With no config file, or with text watermarking disabled, the processor logs a warning and marks nothing. An invalid config file raises an error.
  • It needs a vLLM with the Model Runner V2 logits-processor interface (vllm.v1.worker.gpu.sample.logits_processor). No release has it yet (not 0.19.1, not 0.30.0). The build tested on a GPU is nightly 0.30.1rc1.dev86+g5b3f280a6; export VLLM_USE_V2_MODEL_RUNNER=1 so vLLM cannot fall back to the V1 runner.
  • A request opts in with vllm_xargs.laidline, an object with key_id and scheme (both optional). Over HTTP, send the object JSON-encoded, as in "vllm_xargs": {"laidline": "{\"key_id\": \"k1\", \"scheme\": \"synthid\"}"}. vLLM's OpenAI server accepts only strings, numbers and lists as vllm_xargs values, and answers 400 to a nested object. The Python LLM API also takes a plain dict in SamplingParams.extra_args["laidline"]. The Laidline proxy sends the JSON form for you.
  • SynthID is skipped at temperature 0, so use scheme: kgw for greedy traffic. Speculative decoding is not supported: draft rows are left unmarked.
  • --middleware laidline_vllm.middleware.ack_header adds x-laidline-watermarked: 1 and x-laidline-scheme (the config's scheme, unknown without a usable config) to every response. It means "plugin installed", not "this response was marked"; the Laidline proxy treats unknown as no ack and checks greedy decoding itself. Use the dotted path: vLLM splits it on the last ., in 0.19.1 and in the tested nightly alike. The module:function form fails at startup.

Proven live on an RTX 5080 (SynthID and KGW, directly and through the proxy). Full guide: https://laidline.com/docs/integrations/vllm.

Metadata

Release files for laidline-vllm 1.0.0

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

Source distribution (sdist)

Source distribution for laidline-vllm 1.0.0
File Size Uploaded Provenance Actions
laidline_vllm-1.0.0.tar.gz 14.5 kB With provenance Details for laidline_vllm-1.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for laidline-vllm 1.0.0
File Interpreter ABI Platform Actions
laidline_vllm-1.0.0-py3-none-any.whl Python 3 none any Details for laidline_vllm-1.0.0-py3-none-any.whl

Total release size: 30.9 kB

Release files / laidline_vllm-1.0.0.tar.gz

Download URL laidline_vllm-1.0.0.tar.gz
Size 14.5 kB
Tags Source
SHA-256 checksum
How to use checksums
8e4c1e48297e4e4e471b6980bf2f2af610a16aa1b5dfd87c5998ccc2d563e0c5
BLAKE2b-256 checksum
How to use checksums
c663dfe31aad121320de252c0f208c51529270b49c51fb4b3cbb3121faa2cff7
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 Oct 31, 2026.

Transparency log

Release files / laidline_vllm-1.0.0-py3-none-any.whl

Download URL laidline_vllm-1.0.0-py3-none-any.whl
Size 16.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
69948554e42b04ab6fdeea522b3e5532756cb7764f1755e21bd3314fca547ca3
BLAKE2b-256 checksum
How to use checksums
3bd2575245e364f8da468c41c7e7524409ac5a99bce9b950cd9a8c963502ef3d
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 Oct 31, 2026.

Transparency log

Security for laidline-vllm 1.0.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

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for laidline_vllm-1.0.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 Oct 31, 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.

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