ansible-jsonrpc-server
A JSON-RPC 2.0 server that owns all Ansible execution behind a line-framed stdio seam. It runs Ansible modules and action plugins, gathers facts, and installs collections on behalf of a thin client, so the client never imports Ansible itself.
The server speaks JSON-RPC 2.0 over stdin/stdout with Content-Length framing. It is the
Python runtime behind @sensible-ts/core,
which provisions it into an isolated, version-keyed virtualenv and drives it over that seam.
Install
pip install ansible-jsonrpc-server
Run
python -m ansible_jsonrpc_server
# or the console script
ansible-jsonrpc-server
The process reads JSON-RPC requests on stdin and writes responses on stdout; diagnostics go to stderr.
License
GPL-3.0-or-later. This package depends on and embeds the execution model of
ansible-core (GPL); keeping it isolated in its own process is what lets MIT-licensed
clients drive it without taking on that obligation.
1 maintainer
Metadata
1 maintainer
Release files for ansible-jsonrpc-server 0.0.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 | |
|---|---|---|---|---|
| ansible_jsonrpc_server-0.0.1.tar.gz | 36.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansible_jsonrpc_server-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 72.4 kB
Release files / ansible_jsonrpc_server-0.0.1.tar.gz
| Download URL | ansible_jsonrpc_server-0.0.1.tar.gz |
|---|---|
| Size | 36.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82f4f7f514c583e9bf2c5b90cf883684fa4c1df9b0d8101c1ad8f0b579b2d1a4
|
|
BLAKE2b-256 checksum How to use checksums |
c4e6b67c37f5b881263b8f6118ca56f641f592aa844444d13a72d154b4001adb
|
| 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 21, 2026.
Transparency logRelease files / ansible_jsonrpc_server-0.0.1-py3-none-any.whl
| Download URL | ansible_jsonrpc_server-0.0.1-py3-none-any.whl |
|---|---|
| Size | 35.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2b7ea385107e11d1b90d86931ecdaf88e33dda174088e627e5f0a99ca721b83
|
|
BLAKE2b-256 checksum How to use checksums |
b612a945f6a6e218640b96e751ea7c52abb5d3ca2a662f4c7952204bc0c0218f
|
| 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 21, 2026.
Transparency logSecurity for ansible-jsonrpc-server 0.0.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 ansible_jsonrpc_server-0.0.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 21, 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.
