Screen Stocks Python Bridge
The screenstocks-bridge package is a Python client for the local API exposed
by the Screen Stocks Bridge BepInEx plugin. It requires the plugin to be
installed in the game and the game to be running. The package itself does not
install or contact the game backend; it connects to the plugin on loopback.
Install
python -m pip install screenstocks-bridge
Install the matching BepInEx plugin from the
GitHub releases,
then launch Screen Stocks. The default bridge address is 127.0.0.1:48721.
Read the token from BepInEx/config/screenstocks.bridge.cfg or the BepInEx
log.
Connect
from screenstocks_bridge import BridgeClient
with BridgeClient(token="YOUR_TOKEN") as bridge:
state = bridge.snapshot()
print(state["ready"], state["cash"])
print(bridge.upgrades())
The client supports state and activity reads, trades, upgrade purchases, and auto-action controls. See the bridge usage guide for the full API and its online behavior.
Metadata
Release files for screenstocks-bridge 0.2.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 |
|---|---|---|---|---|
| screenstocks_bridge-0.2.0.tar.gz | 8.1 kB | With provenance | Details for screenstocks_bridge-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| screenstocks_bridge-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for screenstocks_bridge-0.2.0-py3-none-any.whl |
Total release size: 16.5 kB
Release files / screenstocks_bridge-0.2.0.tar.gz
| Download URL | screenstocks_bridge-0.2.0.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
822fbee8a42615bc08cfe2167610e4589a37f3e992159bfbeb22dc9ba701e325
|
|
BLAKE2b-256 checksum How to use checksums |
4b81a5b8c33cd4e81db215a43d0e4a5600ac067bf517189903b58ffd2cdc5b15
|
| 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 4, 2026.
Transparency logRelease files / screenstocks_bridge-0.2.0-py3-none-any.whl
| Download URL | screenstocks_bridge-0.2.0-py3-none-any.whl |
|---|---|
| Size | 8.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
25fb17714169e4b6247e872c9a6cbc19ec5494a153b60759d28dc27735cb19fd
|
|
BLAKE2b-256 checksum How to use checksums |
051ef13097bf6b70bedcd34e273fcccee36583d6eb7ea711f1f370ce460350d6
|
| 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 4, 2026.
Transparency logSecurity for screenstocks-bridge 0.2.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.
Attestation for screenstocks_bridge-0.2.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 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.