vLLM plugins for LLM-jp models
This repository contains vLLM plugins which are necessary to launch LLM-jp models with vLLM entrypoints.
Installation
uv pip install llm-jp-vllm
The above command installs llm-jp-vllm directory onto your environment's site-packages.
Usage
This repository works with the plugin mechanism on vLLM.
vllm serve {llm-jp-4 model} \
--trust-remote-code \
--reasoning-parser llmjp4 \
--reasoning-parser-plugin llm_jp_vllm.llmjp4
Tool calling
The llmjp4 tool parser converts Harmony-format tool calls (including
the parallel call extension of LLM-jp-4) into OpenAI-compatible
tool_calls, for both streaming and non-streaming responses:
vllm serve {llm-jp-4 model} \
--trust-remote-code \
--reasoning-parser llmjp4 \
--reasoning-parser-plugin llm_jp_vllm.llmjp4 \
--enable-auto-tool-choice \
--tool-call-parser llmjp4 \
--tool-parser-plugin llm_jp_vllm.llmjp4
Development
uv sync --all-extras --dev
./checks.sh # ruff / mypy
uv run pytest
1 maintainer
Metadata
1 maintainer
Release files for llm-jp-vllm 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 |
|---|---|---|---|---|
| llm_jp_vllm-0.1.1.tar.gz | 13.1 kB | With provenance | Details for llm_jp_vllm-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| llm_jp_vllm-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for llm_jp_vllm-0.1.1-py3-none-any.whl |
Total release size: 27.7 kB
Release files / llm_jp_vllm-0.1.1.tar.gz
| Download URL | llm_jp_vllm-0.1.1.tar.gz |
|---|---|
| Size | 13.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d45544586f38498227cc611673ca93f223df5b65173cbc0ce58dbbf018a1fafb
|
|
BLAKE2b-256 checksum How to use checksums |
c7e6a50634332f3dd5c9d5745979dfe2af3ca0cffe306b6d44adf513ef215d87
|
| 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 Sep 28, 2026.
Transparency logRelease files / llm_jp_vllm-0.1.1-py3-none-any.whl
| Download URL | llm_jp_vllm-0.1.1-py3-none-any.whl |
|---|---|
| Size | 14.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5091257b495fe5470f2a3a1c5515aa4ca7838932505d67b14629d14de412900e
|
|
BLAKE2b-256 checksum How to use checksums |
a2e65992ad0f160ab13ac988e582a8a38e5a2adb18d94817169bb8570a1bfb55
|
| 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 Sep 28, 2026.
Transparency logSecurity for llm-jp-vllm 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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for llm_jp_vllm-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 Sep 28, 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.
