WSE
WSE is a WebSocket engine for reactive user interfaces: trading terminals, dashboards, monitoring, chats, notifications. Your backend publishes events to topics, and WSE pushes each event to every client subscribed to it, so the screen changes the moment the data does, without polling.
WSE runs inside your backend rather than as a separate service. A Python application starts it with the wse-server package, where it runs in threads of its own, outside the GIL; a Rust application embeds the wse crate. Both are the same engine, written in Rust. Several servers form a cluster by themselves, with no Redis or other broker in between.
In the browser, the TypeScript client keeps the connection, its subscriptions and recovery, on a page without a framework or with React, Vue, Svelte, Angular or Solid; React Native apps use it too. Interfaces written in Rust (Leptos, Yew, Dioxus) use the Rust client compiled to WebAssembly. iOS, Android and Flutter apps, on phones and on desktops, use the Rust client through its Swift, Kotlin and Dart packages. Services and bots connect with the Python or the Rust client, or, on the JVM, in Java or Kotlin.
What it does
- Topics. The backend publishes to topics such as
prices:BTC,orders:user-42orchat:room-7, and clients subscribe by name or by pattern (prices:*). A message can also go to a single connection, or to one worker of a queue group. Each client chooses JSON or MessagePack. - Nothing lost on reconnect. Topics keep their latest messages, and every message carries its position. A client that loses its connection comes back with that position and receives what it missed, in order and without duplicates; if the gap is too old, it is told so and reloads. The clients track positions, drop duplicates and ask for what is missing by themselves.
- Clients that look after themselves. They reconnect with backoff, get a fresh token, and report anything they could not recover. Every client keeps what the user sends in an outbox until the server confirms it, and sends it again after a reconnect, offline meanwhile too; a 3.2 server takes each message once (one it cannot tell it took comes marked a possible repeat), and the application hears what became of each by its id. Every client can keep the outbox on the device, so that it outlives the app. Where every fact counts, every client (TypeScript, Python, Rust, Swift, Kotlin, Dart) can hold a topic after a reconnect until the application has reloaded its state, and recover from what it committed it applied; a send can wait until the topics it depends on are continuous again.
- Presence. Who is on a topic right now, with each user's status or other data, and an event when someone joins or leaves. Several tabs of one user count as one.
- Several instances. In production a backend usually runs as several copies behind a load balancer, each with its own WSE server. The servers link to each other directly: an event published on one copy reaches the subscribers connected to any other, presence covers all of them, and one copy can be drained for a deploy while its clients move to the others. No Redis or other broker sits in between, and each topic goes only to the servers that have subscribers for it.
- Access. Users sign in with a JWT checked during the WebSocket handshake: from a cookie in browsers, from the
Authorizationheader elsewhere. Each connection can be limited to its own topics, by its token or by the application. The server can refuse pages from other sites, and it limits how much and how fast each client may send. - End-to-end encryption. Clients pin the server's public key and every frame is sealed, so a proxy or load balancer that terminates TLS can neither read nor change the traffic. A token that names the client's key opens a connection only for the client that holds the key, so a token seen on the way is of no use.
- Signed messages. Orders, fills and other messages that may be disputed later carry their sender's signature, which can still be checked long after they arrived. The server confirms each one with a signed receipt.
- Speed. The engine delivers on every CPU core: on 12 cores of an Intel Xeon it sends 7.4 to 9.4 million messages a second to 1,000-10,000 subscribers. A publisher faster than its clients is slowed down instead of filling memory.
- Operations. Graceful drain for rolling deploys, health snapshots, Prometheus metrics, limits on connections, message sizes, send rates and memory, and guides for Docker and Kubernetes.
Packages
| Package | Install | Use it for |
|---|---|---|
wse-server |
pip install wse-server |
The server, run from Python |
wse |
cargo add wse |
The server, inside a Rust application (tokio) |
wse-client |
npm install wse-client |
Web interfaces in TypeScript: without a framework, React, Vue, Svelte, Angular, Solid; React Native apps; Electron apps, one connection for every window |
wse-client |
cargo add wse-client |
Interfaces in Rust (WebAssembly), and Rust services on tokio |
tauri-plugin-wse |
cargo add tauri-plugin-wse |
Tauri apps: one connection for every window, on the Rust side (wse-client/tauri in the pages) |
wse-client |
pip install wse-client |
Python services and scripts, with or without asyncio |
wse_client |
flutter pub add wse_client |
Flutter and Dart apps (Android, iOS, macOS, Linux, Windows) |
wse-swift |
Swift Package Manager: https://github.com/silvermpx/wse-swift |
iOS and macOS apps |
wse-client-android |
implementation("io.github.silvermpx:wse-client-android:3.2.0") |
Android apps |
wse-client-jvm |
implementation("io.github.silvermpx:wse-client-jvm:3.2.0") |
Java and Kotlin services and desktop apps on the JVM (Linux, macOS, Windows) |
A server in Python
pip install wse-server
import json
import threading
import time
from wse_server import RustWSEServer
server = RustWSEServer("0.0.0.0", 5007, jwt_secret=b"replace-with-a-strong-secret-key!")
server.enable_drain_mode()
server.start()
print("token:", server.issue_token("user-1"))
def handle_events():
while server.is_running():
for kind, conn_id, data in server.drain_inbound(256, 50):
if kind == "auth_connect": # data: the user id from the token
server.subscribe_connection(conn_id, ["prices"])
elif kind == "msg": # data: the client's message, a dict
print(conn_id, data)
threading.Thread(target=handle_events, daemon=True).start()
price = 100.0
while True:
price += 0.25
server.broadcast("prices", json.dumps({"t": "price", "p": {"symbol": "ACME", "price": price}}))
time.sleep(1)
Clients connect to ws://localhost:5007/wse with the printed token: a browser sends it as the access_token cookie, other clients in the Authorization: Bearer header. Messages are JSON objects with their type in t and their data in p. The rest of the Python API is further down, and runnable examples are in examples/.
A server in Rust
cargo add wse serde_json tokio --features tokio/full
use wse::{Config, Connect, Handler, Inbound, JwtSettings, Server, Subscribe};
/// Every connection joins its user's topic.
struct App;
impl Handler for App {
type Connection = String;
fn connect(&self, connect: &Connect<'_>) -> Option<String> {
let user = connect.user_id?.to_owned();
connect.subscribe(vec![format!("user:{user}")], &Subscribe::default()).ok()?;
Some(user)
}
fn message(&self, user: &mut String, message: Inbound, _size: usize) -> bool {
if let Inbound::Json(message) = message {
println!("{user}: {message}");
}
true
}
fn signed(&self, _user: &mut String, _message: serde_json::Value, _size: usize) -> bool {
false
}
fn disconnect(&self, _user: String) {}
}
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let mut config = Config::default();
config.jwt = Some(JwtSettings::new(std::env::var("JWT_SECRET")?));
let server = Server::new(config)?;
server.start(tokio::net::TcpListener::bind("0.0.0.0:5007").await?, App)?;
let publisher = server.publisher();
publisher.publish("user:42", r#"{"t":"order_filled","p":{"id":7}}"#)?;
publisher.send_to_user("42", r#"{"t":"notice","p":{"text":"hello"}}"#)?;
tokio::signal::ctrl_c().await?;
server.stop().await;
Ok(())
}
The server runs on the application's own tokio runtime. The Handler hears connections and their messages; the Publisher sends to topics, to single connections and to every connection of a user. A complete chat room is in crates/wse/examples/chat.rs, and the crate's own README has the rest.
Clients
TypeScript and React
npm install wse-client
import { useMemo, useState } from 'react';
import { useWSE, type UseWSEConfig } from 'wse-client';
export function Price() {
const [price, setPrice] = useState<number>();
const config = useMemo<UseWSEConfig>(() => ({
endpoints: ['wss://example.com/wse'],
registerHandlers: (processor) => {
processor.registerHandler('price', (msg) => setPrice(msg.p.price));
},
}), []);
const { connectionHealth } = useWSE('cookie', ['prices'], config);
return <p>{connectionHealth}: {price ?? '-'}</p>;
}
A browser cannot put headers on a WebSocket, so it signs in with the cookie your login endpoint sets (access_token); 'cookie' tells the hook to connect. Every useWSE() on a page shares one connection. Without React, createWSEClient from wse-client/core makes a client of its own, which wse-client/react, wse-client/vue, wse-client/svelte, wse-client/angular and wse-client/solid hand to components and wse-client/react-native sets up for an app. wse-client/bridge keeps one connection for every window of an application, with owners ready for Electron (wse-client/electron) and Tauri (wse-client/tauri with the tauri-plugin-wse crate). More in the TypeScript client's README.
Python
pip install wse-client
import asyncio
from wse_client import connect
async def main():
async with connect("ws://localhost:5007/wse", token="<token>", topics=["prices"]) as client:
async for event in client:
print(event.type, event.payload)
asyncio.run(main())
SyncWSEClient does the same without asyncio. More in the Python client's README.
Rust
cargo add wse-client tokio --features tokio/full
#[tokio::main]
async fn main() -> Result<(), wse_client::Error> {
let mut config = wse_client::Config::new("ws://localhost:5007/wse");
config.token = Some("<token>".into());
config.topics = vec!["prices".into()];
let (_client, mut events) = wse_client::connect(config).await?;
while let Some(incoming) = events.next().await {
println!("{incoming:?}");
}
Ok(())
}
The same crate builds for the browser (wasm32-unknown-unknown), for Leptos, Yew or Dioxus apps, with the same API. A Handler can read each message straight from its frame into your own types, without copying it. More in the Rust client's README.
Swift, Kotlin, Java and Flutter
iOS, Android and Flutter apps use the Rust client through packages of their own: the same reconnects, recovery, end-to-end encryption and signed messages, with async calls and the events as a stream, and helpers that pause the connection while the app is in the background or offline. The Kotlin package also runs on the JVM (wse-client-jvm, Java 17 and newer, Linux, macOS and Windows), and Java calls it with futures.
let client = try await WseClient.connect(
WseConfig(url: "wss://example.com/wse", token: token, topics: ["prices"]))
for try await item in client.events() {
if case let .message(message) = item { print(message.kind, message.json ?? "") }
}
val client = connectClient(WseConfig(url = "wss://example.com/wse", token = token, topics = listOf("prices")))
client.events().asFlow().collect { item ->
if (item is WseItem.Message) println("${item.message.kind}: ${item.message.json}")
}
WseClient client = Wse.connect(Wse.config("wss://example.com/wse").token(token).topics("prices").build()).join();
WseEventReader events = Wse.events(client);
for (WseItem item; (item = events.next()) != null; ) {
if (item instanceof WseItem.Message m) System.out.println(m.getMessage().getKind() + ": " + m.getMessage().getJson());
}
final client = await WseClient.connect(
wseConfig('wss://example.com/wse', token: token, topics: ['prices']),
);
await for (final item in client.events()) {
if (item.kind == WseItemKind.message) print('${item.name}: ${item.json}');
}
More in the READMEs of the Swift, Kotlin and Dart packages.
The Python server
Everything here is a method or an option of RustWSEServer. The integration guide has the complete reference.
Options
Sizes are in bytes, times in seconds.
| Option | Default | |
|---|---|---|
host, port |
required | The address to listen on (::: IPv6 and IPv4) |
max_connections |
1000 | Connections at once |
jwt_secret |
None |
The key that checks tokens: the shared secret for HS256/384/512 (at least 32, 48 or 64 bytes), or the PEM public key for the RSA, ECDSA and EdDSA algorithms. Without it the application checks each connection itself and calls accept_connection() |
jwt_algorithm |
"HS256" |
The algorithm tokens must use; a token's own alg header never overrides it |
jwt_issuer, jwt_audience |
None |
The iss and aud a token must carry |
jwt_key_id |
None |
The kid a token must carry |
jwt_cookie_name |
"access_token" |
The cookie a browser's token is read from |
jwt_previous_secret |
None |
The previous key, still accepted while clients move to the new one |
jwt_private_key |
None |
The PEM private key issue_token() signs with, for the RSA, ECDSA and EdDSA algorithms |
allowed_origins |
None |
The origins browsers may connect from ("https://app.example.com"); others get HTTP 403 |
client_subscriptions |
False |
Let clients subscribe, unsubscribe and recover by themselves, within their topic ACL. Otherwise their requests reach the application as messages |
max_subscriptions_per_connection |
0 | Topics per connection (0: no limit) |
recovery_enabled |
False |
Keep each topic's recent messages for clients that reconnect |
recovery_buffer_size |
128 | Messages kept per topic, rounded up to a power of two |
recovery_ttl |
300 | How long a quiet topic's messages are kept |
recovery_max_messages |
500 | Messages replayed for one request at most |
recovery_memory_budget |
256 MB | Memory for the kept messages of all topics |
presence_enabled |
False |
Track who is on each topic |
presence_max_data_size |
4096 | A user's presence data at most |
presence_max_members |
0 | Members per topic (0: no limit) |
max_message_size |
1 MB | The largest frame a client may send |
rate_limit_capacity |
100000 | Messages a client may send in a burst (float("inf"): no limit) |
rate_limit_refill |
10000 | Messages per second a client may send after the burst |
max_outbound_queue_bytes |
16 MB | Data waiting to be written to one client. Past it the client misses messages, and one over it for two pings is closed (code 1013) |
max_inbound_queue_size |
131072 | Client messages waiting for the application before new ones are dropped (a message of a 3.2 client's outbox is refused instead, as busy, and its client hears so). Connect, disconnect and presence events are never dropped |
max_inbound_queue_bytes |
64 MB | The same limit in bytes |
ping_interval |
25 | Time between the server's pings |
idle_timeout |
60 | A client silent this long is closed (code 4408) |
e2e_identity_key |
None |
PEM or DER (PKCS#8) P-256 private key the server proves itself with in end-to-end encryption |
e2e_legacy |
True |
Also serve 2.x clients' encryption, which has no server identity; False refuses it (code 4800) |
signing_key |
None |
PEM or DER (PKCS#8) P-256 private key for signed messages |
signature_window |
30 | How far a client's signed message may be off the server's clock |
bind_sessions |
True |
A token that names the client's key (cnf) is taken only on an end-to-end session in which the client proves that key; False keeps the key for signed messages only |
Events
The application reads what clients do in batches:
server.enable_drain_mode() # before start()
events = server.drain_inbound(256, 50) # up to 256 events; waits up to 50 ms for the first
Each event is a tuple (kind, conn_id, data):
| Kind | When | data |
|---|---|---|
"auth_connect" |
A client connected with a valid token | its user id (the token's sub) |
"connect" |
A client connected to a server without jwt_secret |
its Cookie header: check it, then call accept_connection(conn_id, user_id) |
"msg" |
A JSON message | the message, a dict |
"signed" |
A signed message that passed every check | its fields, and signature (body, sig, kid): the proof to keep |
"raw" |
Text that is not JSON | the string |
"bin" |
A binary frame | the bytes |
"disconnect" |
The connection closed | None |
"presence_join" |
A user's first connection joined a topic | user_id, topic and data |
"presence_leave" |
A user's last connection left a topic | user_id, topic and data |
A message from a 3.2 client's outbox carries its number there (s) and its id. The server takes each once; one it cannot tell it took already comes with possible_repeat: True, and the application checks its id against what it applied.
Instead of polling, set_callbacks(on_connect, on_message, on_disconnect, on_signed_message=None) has the server call the application on its worker threads, each connection's callbacks in the order of its events.
Sending
server.send(conn_id, text) # to one connection
server.send_bytes(conn_id, data) # binary, to one connection
server.send_event(conn_id, {"t": "notice", "p": {"text": "hi"}}) # a dict, compressed when large
server.broadcast(topic, text) # to a topic's subscribers on every server of the cluster
server.broadcast_local(topic, text) # to a topic's subscribers on this server
server.broadcast_all(text) # to every connection on this server
server.broadcast_all_bytes(data)
server.send_to_user(user_id, text) # to every tab and device of a user on this server
server.send_event_to_user(user_id, {"t": "notice", "p": {}})
server.disconnect_user(user_id) # close them all: a logout, a revoked session
A client that asked for MessagePack gets MessagePack from all of these except the two _bytes methods, which send their bytes as they are. When the server has 65,536 commands queued, these calls wait (without holding the GIL), so a publisher faster than its clients cannot run the server out of memory.
Topics
server.set_topic_acl(conn_id, allow=["user:42:*"], deny=["user:42:admin"])
server.subscribe_connection(conn_id, ["user:42:orders", "user:42:alerts:*"]) # returns the topics it took
server.subscribe_connection(conn_id, ["chat"], {"status": "online"}) # with presence data
server.subscribe_connection(conn_id, ["jobs"], queue_group="workers") # one of "workers" gets each message
server.unsubscribe_connection(conn_id, ["chat"]) # or None: every topic
server.get_topic_subscriber_count("chat")
The ACL takes * and ? wildcards, and a deny wins over an allow. Set it before subscribing; a token can carry the same rules in its wse_topics claim. A pattern subscription gets only the topics the ACL allows.
Presence
With presence_enabled=True:
server.presence("chat") # {"alice": {"data": {"status": "online"}, "connections": 2}, ...}
server.presence_stats("chat") # {"num_users": 2, "num_connections": 3}
server.update_presence(conn_id, {"status": "away"})
A user is the token's sub, so two tabs of one user are one member.
Recovery
With recovery_enabled=True, every message published to a topic carries its position: tp, e and o (topic, epoch, offset). The clients in this repository track it, drop duplicates, notice gaps and ask for what they missed. With client_subscriptions=True the server answers them itself; otherwise the application does:
server.subscribe_with_recovery(conn_id, ["prices"], recover=True, epoch=epoch, offset=offset)
# {"recovered": True, "topics": {"prices": {"epoch": "0000007b", "offset": 456, "recovered": True, "count": 12, ...}}}
When the missed messages are no longer kept, recovered is False and the client has to reload.
Cluster
openssl rand -base64 32 # the cluster's secret: the same on every server
server.connect_cluster(
peers=["10.0.0.2:9999", "10.0.0.3:9999"],
cluster_port=9999,
cluster_secret=os.environ["WSE_CLUSTER_SECRET"],
)
server.broadcast("prices", text) # reaches the subscribers on every server
The links between servers are TLS, always. Each server derives the same key from the secret and proves it when a link opens, so a server without the secret cannot join, and nothing between them can read or change the traffic. No certificates to make; a company CA can sign them instead (tls_cert, tls_key, tls_ca). A new server can also join through one seed address (seeds=[...], cluster_addr=...), and the links can share the WebSocket port (single_port=True). cluster_info() lists the linked peers. With recovery on, a link between two servers that drops and comes back loses nothing that either server still holds: each gets what it missed from the other, in order, before anything new, and a client whose recovery reaches back past what is gone is told so (recovered: false). Addresses are host:port; an IPv6 address gives its zone by number ([fe80::1%2]:9999). The protocol is described in CLUSTER_PROTOCOL.md.
Running it
server.drain(4300, "deploy", timeout=30) # refuse new clients, close the rest, wait; returns how many it forced
server.stop()
server.health_snapshot() # connections, queues, recovery, cluster and presence
server.prometheus_metrics() # text for a /metrics endpoint
with RustWSEServer(...) as server: starts the server and stops it at the end. Logs go to standard output at level info; RUST_LOG=wse=debug shows more.
Security
- Tokens.
issue_token(sub, ttl=900, claims=None)signs tokens with the server's own settings, for a login endpoint in the same process, andreload_jwt_keys()replaces the keys of a running server. A connection is closed when its token expires (code 4403), and the clients reconnect with a fresh one. - TLS. Serve
wss://through a reverse proxy or a load balancer (nginx, Caddy); the server itself speaks plain WebSocket. Links between the servers of a cluster are always TLS, from the cluster's secret or from certificates. - Browsers.
allowed_originsrefuses pages from other sites, which could otherwise connect with your users' cookies. - Limits. Clients are rate-limited on what they send, and one that keeps going over is closed (code 4429). Frame sizes, subscriptions, queues and connections waiting in the handshake are all bounded.
End-to-end encryption
openssl genpkey -algorithm EC -pkeyopt ec_paramgen_curve:P-256 -out e2e-identity.pem
server = RustWSEServer(
"0.0.0.0", 5007,
jwt_secret=secret,
e2e_identity_key=open("e2e-identity.pem", "rb").read(),
)
print(server.e2e_identity_public_key()) # the key clients pin
Clients pin that key: encryption=True, e2e_server_keys=[key] in Python, security: { encryptionEnabled: true, serverKeys: [key] } in TypeScript, Encryption::pinned([key]) in Rust. Each direction then has its own AES-256-GCM key; frames are numbered, and a replayed, reordered or forged frame ends the connection.
The token still passes whatever terminates TLS. A token that names the client's key in its cnf claim is of no use there: the client signs the session's handshake with that key, and the server admits the connection only when the signature matches the key in the token. Clients with encryption on and a signing_key do this by themselves, and stop if the server does not confirm their key.
Signed messages
fill = server.sign("fill", {"order": "o-17", "qty": "2"}, topic="orders:u1")
server.broadcast("orders:u1", fill) # signed once, sent to any number of clients
Clients check such messages against the server's signing_public_key(), which they pin. They sign their own with a key that stays on the device: send(..., signed=True) in Python, sendSigned() in TypeScript, send_signed() in Rust. The server accepts each one once, within signature_window, and only with the key bound to that user, by the token's cnf claim or by set_client_key(). A message the server signs for one user names them, server.sign("fill", {...}, to=user_id): the proof shows whom it was for, and other users' clients drop it.
Setup, key rotation and what each guarantees: SECURITY.md.
Performance
A broadcast is encoded once and written out by every CPU core in parallel, each core serving its share of the connections. A publisher faster than its clients is slowed down rather than allowed to fill memory.
3.0 against 2.5.1 on the same machine (Intel Xeon Gold 5412U, 24 cores), with the server and the benchmark client on separate cores:
| Test | 2.5.1 | 3.0 |
|---|---|---|
| Broadcast to 1,000 / 5,000 / 10,000 subscribers | 5.4 / 6.0 / 7.4M deliveries/s | 9.4 / 8.2 / 7.4M |
| A topic through a cluster peer, 1,000 / 10,000 subscribers | 5.9 / 5.7M deliveries/s | 6.8 / 8.4M |
| Messages from clients, 100 / 1,000 connections | 8.3 / 7.7M msg/s | 8.3 / 7.7M |
| Peak memory under a publisher that never pauses | 35-39 GB | 19-21 GB |
More results: benchmarks, fan-out, and the Rust, Python and TypeScript clients.
Upgrading from 2.x
The Python API keeps its names, but some behaviour changed. What most applications notice:
connect_cluster()needscluster_port(orsingle_port=True), and the cluster's secret (cluster_secret) or TLS certificates: links between servers are always TLS.start()raisesOSErrorwhen the port is taken;drain()waits for the clients and returns how many it had to drop.- JWT settings are checked at startup, and a token without the configured
issoraudis refused. - End-to-end encryption now authenticates the server, so clients pin its key. 2.x clients keep working while
e2e_legacy=True, the default. - The rate limit applies to what clients send;
send_event()is no longer throttled.
The full list, with the client changes: MIGRATION.md.
Documentation
- Integration guide: setup and the complete API
- Clients: TypeScript, Python, Rust, Swift, Kotlin and Java, Dart, Tauri
- Conformance: the cases every client is checked against
- Migration guide: from 2.x to 3.0, from 3.0 to 3.1, and from 3.1 to 3.2
- Wire protocol: messages, close codes, end-to-end encryption
- Cluster protocol
- Security
- Deployment: production setup, Docker, Kubernetes
- Architecture: how the server works inside
- Rust utilities: queues, rate limiters, compression, crypto and JWT helpers the Python package also exports
- Changelog
- Contributing
License
MIT
Metadata
Release files for wse-server 3.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 |
|---|---|---|---|---|
| wse_server-3.2.0.tar.gz | 398.2 kB | With provenance | Details for wse_server-3.2.0.tar.gz |
Built distributions (wheels)
Total release size: 87.0 MB
Release files / wse_server-3.2.0.tar.gz
| Download URL | wse_server-3.2.0.tar.gz |
|---|---|
| Size | 398.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
843d483b182ec3ce4db8f2b56dd031e13693027910512b8e4d5dca219a543f74
|
|
BLAKE2b-256 checksum How to use checksums |
5e9b8e73a88dea888291d6e358ab5dc7326192d6fcf27d98044950c131cc8fe6
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp315-cp315t-win_arm64.whl
| Download URL | wse_server-3.2.0-cp315-cp315t-win_arm64.whl |
|---|---|
| Size | 4.2 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading Windows ARM64 |
|
SHA-256 checksum How to use checksums |
cbb7cd936ff2d117b7b451f9333cfc3c8811b3e64da92ede964b4f07f6c65996
|
|
BLAKE2b-256 checksum How to use checksums |
f25f86962d259cd38211ed3ad975fe010774202a290da1a5fe85ee00d905f8ec
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp315-cp315t-win_amd64.whl
| Download URL | wse_server-3.2.0-cp315-cp315t-win_amd64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b1725adb497ba56f7cb815093d1ce1061ececc512f362475b39bd29359584647
|
|
BLAKE2b-256 checksum How to use checksums |
605048fe81e12f17247d6b8ade7f0fe1fdc23d73ce2bce54cd7da1b702bc9cf9
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp315-cp315t-manylinux_2_28_aarch64.whl
| Download URL | wse_server-3.2.0-cp315-cp315t-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
94103712091fa3c49fbf341458b2367dedfa60461c454a94a6fdb2ea313045b0
|
|
BLAKE2b-256 checksum How to use checksums |
17c70b6054b97b34fdacc096398e06eecb5fdc0eed142f801d6960053e6bd213
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | wse_server-3.2.0-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
a8af5c32c5e0f930d9b361ff4b74077f5a6c2b9aaf2075bb7efc45e4fdf7f359
|
|
BLAKE2b-256 checksum How to use checksums |
5890248717100a92cd90bd8d7ead1a450ce5d30309377aa879eb0ab021ab8317
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp315-cp315t-macosx_11_0_arm64.whl
| Download URL | wse_server-3.2.0-cp315-cp315t-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1e944b8d0b93c715c23c33fcfb9b8c672599452cc1d52ddc590e61dd755a3bdf
|
|
BLAKE2b-256 checksum How to use checksums |
64739d411ba809fa889f8ef4d1b71ad378196137914522be85c1b5c17a98a367
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp315-cp315t-macosx_10_12_x86_64.whl
| Download URL | wse_server-3.2.0-cp315-cp315t-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
356b59303aac1e0a0c6b949e68476f1d0d83ababe54df7aa26e94392fdc18a51
|
|
BLAKE2b-256 checksum How to use checksums |
4762d0231fa6da6311c13340e2339cdc6a0972eaf49c9cea073747dbb6363f46
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp314-cp314t-win_arm64.whl
| Download URL | wse_server-3.2.0-cp314-cp314t-win_arm64.whl |
|---|---|
| Size | 4.2 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows ARM64 |
|
SHA-256 checksum How to use checksums |
776b0606870b60988bfcdcb7828bc6a9fda9b6ce978a55e0678ce9079fab405c
|
|
BLAKE2b-256 checksum How to use checksums |
7b490c1cb01eae41a42f3123d13573651a7a6404f31e60e60ae293d6469190cf
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp314-cp314t-win_amd64.whl
| Download URL | wse_server-3.2.0-cp314-cp314t-win_amd64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9d572b4986db91227740f652f5d05f8f113df9c6c31a40e77e05cdb979653ec0
|
|
BLAKE2b-256 checksum How to use checksums |
bdb061d7667c9a074d02cd2bac666e56221c426cc34db25470df5dc9969df874
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp314-cp314t-manylinux_2_28_aarch64.whl
| Download URL | wse_server-3.2.0-cp314-cp314t-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
dee8f88ecf1d66e16018948228f6849afb0ba3554f9ac4f23b8494f6dcc61acf
|
|
BLAKE2b-256 checksum How to use checksums |
eaff7733d7630c77c19b957edea412fd100c911f1783cb8c592228abd420bc7c
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | wse_server-3.2.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
6f9bec218c1a640ba4bb8bc636c1f536bb2926255c9906251666b697c5195cc2
|
|
BLAKE2b-256 checksum How to use checksums |
9d97240b3036c5a3fed2d206945de819bc23bcfede6a927d846043eef50e8503
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp314-cp314t-macosx_11_0_arm64.whl
| Download URL | wse_server-3.2.0-cp314-cp314t-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
12799226d506356b6d0a3fb5b90758b5fc212a329ce760a9fb102ebeb8a5896d
|
|
BLAKE2b-256 checksum How to use checksums |
d9e560c1622ca2a27b5557103f81b4e77a83e95dbdbddfbc9fbb50e2988ae9fd
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp314-cp314t-macosx_10_12_x86_64.whl
| Download URL | wse_server-3.2.0-cp314-cp314t-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
23ca8c900d2788f06552ec4c51ffd8d36c28e870a8e7a02635f8ad2009536abc
|
|
BLAKE2b-256 checksum How to use checksums |
205315c33911b19091b1b50a5df412bab6a67cb2e08121d30f13989051feca73
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp312-abi3-win_arm64.whl
| Download URL | wse_server-3.2.0-cp312-abi3-win_arm64.whl |
|---|---|
| Size | 4.2 MB |
| Tags | CPython 3.12 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
0193c61753b5b2a4f43529538b909812baed62a407a445e052d4263db76dd05f
|
|
BLAKE2b-256 checksum How to use checksums |
fc15e5f38ff6507c375f46fada6c7ce27fd0d8c10dd7a4a38b02c710df10c7e5
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp312-abi3-win_amd64.whl
| Download URL | wse_server-3.2.0-cp312-abi3-win_amd64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.12 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
eeab0e206c6c79c6bb7c583ab5ca69b0cc4bf45e0fe80f5ffe5a6eb2cb677415
|
|
BLAKE2b-256 checksum How to use checksums |
0c05a7b81b7c41288745aa02f9758c3a3615733ffda8150445f9320d26a366b2
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp312-abi3-musllinux_1_2_x86_64.whl
| Download URL | wse_server-3.2.0-cp312-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 4.8 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
dd337694feb15b3c566a56085409f91fa0344cca0fc3c2065c798b9bc186f97e
|
|
BLAKE2b-256 checksum How to use checksums |
140940d7a4d936305c6ec353c048a6afbf5146af0b86094f5f86c9f8889ea61b
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp312-abi3-musllinux_1_2_aarch64.whl
| Download URL | wse_server-3.2.0-cp312-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | CPython 3.12 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
ee04071a3bbd102cc656a0bf8491a80120bf07267c8de113737c0390136f0046
|
|
BLAKE2b-256 checksum How to use checksums |
159c48dafcf0aba98da8d2aa70a74bf63e9c74fc47f4179ed43dc5a7aaa82a53
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp312-abi3-manylinux_2_28_aarch64.whl
| Download URL | wse_server-3.2.0-cp312-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
18f7e768c42164b9cec823ac77d9d17f5d44923ce1418bbcc42c0f32b8c57032
|
|
BLAKE2b-256 checksum How to use checksums |
3eca66530b1bb3188c001978003344f514f2ef451a8152f63dca331dd1ae8637
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | wse_server-3.2.0-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
bb3ff36de0a75e2f8fc766bc924693629ace23be8cae6adc760630f873b9c2e0
|
|
BLAKE2b-256 checksum How to use checksums |
469cdfd8f598ac5e5fbc520daf8785d54974bcbe2f728118db23013e541667ac
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp312-abi3-macosx_11_0_arm64.whl
| Download URL | wse_server-3.2.0-cp312-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.12 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
fb8000e2c7518d71ed979da47cfa5de9cb2754e33d2438f859f376a37c08445d
|
|
BLAKE2b-256 checksum How to use checksums |
4b47631d5ff16bb60df8873f1e9ad8a42bf53550a5677548fe55c09bc0b131ba
|
| 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 Nov 19, 2026.
Transparency logRelease files / wse_server-3.2.0-cp312-abi3-macosx_10_12_x86_64.whl
| Download URL | wse_server-3.2.0-cp312-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | CPython 3.12 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
abe792746fe056697d797b8d8d20a2e7f69eb9102ee69309034b6083acaa315b
|
|
BLAKE2b-256 checksum How to use checksums |
70f614a2593fbe2b970eaee8eea9aa0397d2b04dc2b792a5808669e5c124d4af
|
| 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 Nov 19, 2026.
Transparency logSecurity for wse-server 3.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 21 files in this release have been uploaded with provenance metadata.
Attestation for wse_server-3.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 Nov 19, 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.