Skip to main content

WSE

PyPI - Server PyPI - Client npm crates.io - Server crates.io - Client License: MIT

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 one connection per page, with its subscriptions and recovery, and gives React a hook; interfaces written in Rust (Leptos, Yew, Dioxus) use the Rust client compiled to WebAssembly. Services and bots connect with the Python or the Rust client.

What it does

  • Topics. The backend publishes to topics such as prices:BTC, orders:user-42 or chat: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. The TypeScript and Python clients can also keep what the user sends while offline and deliver it once the connection is back.
  • 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 Authorization header 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, with a React hook
wse-client cargo add wse-client Interfaces in Rust (WebAssembly), and Rust services on tokio
wse-client pip install wse-client Python services and scripts, with or without asyncio

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. 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.

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
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. 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

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: each gets what it missed from the other, in order, before anything new. 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, and reload_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_origins refuses 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() needs cluster_port (or single_port=True), and the cluster's secret (cluster_secret) or TLS certificates: links between servers are always TLS.
  • start() raises OSError when 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 iss or aud is 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

License

MIT

Metadata

Release files for wse-server 3.0.1

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

Source distribution (sdist)

Source distribution for wse-server 3.0.1
File Size Uploaded Provenance Actions
wse_server-3.0.1.tar.gz 323.7 kB With provenance Details for wse_server-3.0.1.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for wse-server 3.0.1
File Actions
wse_server-3.0.1-cp315-cp315t-win_arm64.whl CPython 3.15 CPython 3.15 free-threading Windows ARM64 Details for wse_server-3.0.1-cp315-cp315t-win_arm64.whl
wse_server-3.0.1-cp315-cp315t-win_amd64.whl CPython 3.15 CPython 3.15 free-threading Windows x86-64 Details for wse_server-3.0.1-cp315-cp315t-win_amd64.whl
wse_server-3.0.1-cp315-cp315t-manylinux_2_28_aarch64.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.28+ ARM64 Details for wse_server-3.0.1-cp315-cp315t-manylinux_2_28_aarch64.whl
wse_server-3.0.1-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64 Details for wse_server-3.0.1-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
wse_server-3.0.1-cp315-cp315t-macosx_11_0_arm64.whl CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64 Details for wse_server-3.0.1-cp315-cp315t-macosx_11_0_arm64.whl
wse_server-3.0.1-cp315-cp315t-macosx_10_12_x86_64.whl CPython 3.15 CPython 3.15 free-threading macOS 10.12+ x86-64 Details for wse_server-3.0.1-cp315-cp315t-macosx_10_12_x86_64.whl
wse_server-3.0.1-cp314-cp314t-win_arm64.whl CPython 3.14 CPython 3.14 free-threading Windows ARM64 Details for wse_server-3.0.1-cp314-cp314t-win_arm64.whl
wse_server-3.0.1-cp314-cp314t-win_amd64.whl CPython 3.14 CPython 3.14 free-threading Windows x86-64 Details for wse_server-3.0.1-cp314-cp314t-win_amd64.whl
wse_server-3.0.1-cp314-cp314t-manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ ARM64 Details for wse_server-3.0.1-cp314-cp314t-manylinux_2_28_aarch64.whl
wse_server-3.0.1-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Details for wse_server-3.0.1-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
wse_server-3.0.1-cp314-cp314t-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 Details for wse_server-3.0.1-cp314-cp314t-macosx_11_0_arm64.whl
wse_server-3.0.1-cp314-cp314t-macosx_10_12_x86_64.whl CPython 3.14 CPython 3.14 free-threading macOS 10.12+ x86-64 Details for wse_server-3.0.1-cp314-cp314t-macosx_10_12_x86_64.whl
wse_server-3.0.1-cp312-abi3-win_arm64.whl CPython 3.12 abi3 Windows ARM64 Details for wse_server-3.0.1-cp312-abi3-win_arm64.whl
wse_server-3.0.1-cp312-abi3-win_amd64.whl CPython 3.12 abi3 Windows x86-64 Details for wse_server-3.0.1-cp312-abi3-win_amd64.whl
wse_server-3.0.1-cp312-abi3-musllinux_1_2_x86_64.whl CPython 3.12 abi3 Linux musl 1.2+ x86-64 Details for wse_server-3.0.1-cp312-abi3-musllinux_1_2_x86_64.whl
wse_server-3.0.1-cp312-abi3-musllinux_1_2_aarch64.whl CPython 3.12 abi3 Linux musl 1.2+ ARM64 Details for wse_server-3.0.1-cp312-abi3-musllinux_1_2_aarch64.whl
wse_server-3.0.1-cp312-abi3-manylinux_2_28_aarch64.whl CPython 3.12 abi3 Linux glibc 2.28+ ARM64 Details for wse_server-3.0.1-cp312-abi3-manylinux_2_28_aarch64.whl
wse_server-3.0.1-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl CPython 3.12 abi3 Linux glibc 2.17+ x86-64 Details for wse_server-3.0.1-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
wse_server-3.0.1-cp312-abi3-macosx_11_0_arm64.whl CPython 3.12 abi3 macOS 11.0+ ARM64 Details for wse_server-3.0.1-cp312-abi3-macosx_11_0_arm64.whl
wse_server-3.0.1-cp312-abi3-macosx_10_12_x86_64.whl CPython 3.12 abi3 macOS 10.12+ x86-64 Details for wse_server-3.0.1-cp312-abi3-macosx_10_12_x86_64.whl

Total release size: 84.0 MB

Release files / wse_server-3.0.1.tar.gz

Download URL wse_server-3.0.1.tar.gz
Size 323.7 kB
Tags Source
SHA-256 checksum
How to use checksums
f77be072fe53349f376e1386c8bcd3530b52fa3b70fe5390eec00839e600e658
BLAKE2b-256 checksum
How to use checksums
12db8ef8c00667523e57472c3aeccd77f03e54e9581df3ebf525318a8f725928
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp315-cp315t-win_arm64.whl

Download URL wse_server-3.0.1-cp315-cp315t-win_arm64.whl
Size 4.0 MB
Tags CPython 3.15 CPython 3.15 free-threading Windows ARM64
SHA-256 checksum
How to use checksums
66bda5a75fac9888e53b26e8ce803dcb0e8150004ddee41b8c61f6363138e9b0
BLAKE2b-256 checksum
How to use checksums
8e89fec786ab65e200382e9751aefd8f25de4b313e31922ba1f453dcc4c8a788
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp315-cp315t-win_amd64.whl

Download URL wse_server-3.0.1-cp315-cp315t-win_amd64.whl
Size 4.1 MB
Tags CPython 3.15 CPython 3.15 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
1f4d75a2dd1c044601a682f306cec6aad54449b4f464d1f7599f0eff3183927a
BLAKE2b-256 checksum
How to use checksums
c9bed19d8655d6b9619b1af35e5880acc27f2b1121ab69170d67b444b89934d7
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp315-cp315t-manylinux_2_28_aarch64.whl

Download URL wse_server-3.0.1-cp315-cp315t-manylinux_2_28_aarch64.whl
Size 4.2 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
b42917b337951acf61f9ebe9c192a74c8b6b19fc00af3d9b61568e26c38a3fe9
BLAKE2b-256 checksum
How to use checksums
d0bea13bb1418d34b32a4ebd7dfdb506956b8e1ef0b22f7c4f93c6921d372c6f
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL wse_server-3.0.1-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 4.4 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
abac7d898c6770c2b668bf8e16d9611fa07ef255c4b30106d65af996ad149e18
BLAKE2b-256 checksum
How to use checksums
684c954c8b511e13c7f609bd624ff8966be8f67b5374e2c6e89848e2c8eaf852
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp315-cp315t-macosx_11_0_arm64.whl

Download URL wse_server-3.0.1-cp315-cp315t-macosx_11_0_arm64.whl
Size 3.9 MB
Tags CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
d3c7bde19fc9895f99617e2ea3801e9c96631d6688587932d950010eff9e75da
BLAKE2b-256 checksum
How to use checksums
d8e6d9b535f2eb67c1232ebf86b19557c058f967b1cee813d8381e18c441d6e0
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp315-cp315t-macosx_10_12_x86_64.whl

Download URL wse_server-3.0.1-cp315-cp315t-macosx_10_12_x86_64.whl
Size 4.3 MB
Tags CPython 3.15 CPython 3.15 free-threading macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
dc95be13f17f67661f2a16d34667a85f1cde4b20a3b43e046bbecd121fe23fe5
BLAKE2b-256 checksum
How to use checksums
f8b27238ec049b76e50cac6ed3ad89c36d7451465f7331a542af7ca03aa57bea
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp314-cp314t-win_arm64.whl

Download URL wse_server-3.0.1-cp314-cp314t-win_arm64.whl
Size 4.0 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows ARM64
SHA-256 checksum
How to use checksums
d593bf29833a9a0e4b99fb64c14734ff4d28f619ab0f71dd8fa7786db7dc7bd3
BLAKE2b-256 checksum
How to use checksums
3e824aefe90f16d59d91cf9003823659e114ef3e9f27acf36dbde9f85b667e86
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp314-cp314t-win_amd64.whl

Download URL wse_server-3.0.1-cp314-cp314t-win_amd64.whl
Size 4.1 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
a5e8f60c1aa42b7252f38e87cfe6f6c1b03d4aa5a5e2108b00ed84c0f1a5a837
BLAKE2b-256 checksum
How to use checksums
084bab1fdb2550e1ae81ae026cac2a80d1701eba9d3289c8756fa79df33e0cf3
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp314-cp314t-manylinux_2_28_aarch64.whl

Download URL wse_server-3.0.1-cp314-cp314t-manylinux_2_28_aarch64.whl
Size 4.2 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
b1ff4aa93974f7539f0160cec98c833c2538a9271bc49e7c0748835003815bcd
BLAKE2b-256 checksum
How to use checksums
4e368196f5395569d9fdb84abfe003397fb4cb038606374b6d933144df2387a1
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL wse_server-3.0.1-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 4.4 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
b1bfa80c8d4c46745ede832658aea4ef04a57e2e13d810792aa791b297a4a158
BLAKE2b-256 checksum
How to use checksums
64ae585f592740629bea26cc5c3a1c7ca1b20746c1753c83da5e91bd7b1815bc
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp314-cp314t-macosx_11_0_arm64.whl

Download URL wse_server-3.0.1-cp314-cp314t-macosx_11_0_arm64.whl
Size 3.9 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
b5eb22bebd590e1afcce7465a4b3462461972df87201d68ae4978d8317e5e285
BLAKE2b-256 checksum
How to use checksums
e32fa277b05c126f60af2200215cb6db253702aa43c8a517d561c3778bb837a2
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp314-cp314t-macosx_10_12_x86_64.whl

Download URL wse_server-3.0.1-cp314-cp314t-macosx_10_12_x86_64.whl
Size 4.3 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
c81bab2b897ff44ba8a5dbe511af3b305530fad973658f256cbb897584ea8aaf
BLAKE2b-256 checksum
How to use checksums
6125aeb172bfbb2a9cdea897e70bead9d9f41aa1f499431fe844f176d6c67aa6
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp312-abi3-win_arm64.whl

Download URL wse_server-3.0.1-cp312-abi3-win_arm64.whl
Size 4.0 MB
Tags CPython 3.12 Windows ARM64 abi3
SHA-256 checksum
How to use checksums
259fdc9ae7a77909c443b4f7f30d7c9430dc6f6b747cefc469a427a9a908a3fa
BLAKE2b-256 checksum
How to use checksums
221987a31ea56263984dd63f0744b0eafaa8093f5316b027dfc2c25621cd7193
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp312-abi3-win_amd64.whl

Download URL wse_server-3.0.1-cp312-abi3-win_amd64.whl
Size 4.1 MB
Tags CPython 3.12 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
fc26fdde912bc2ccf4adaf09d1b1d1ca3350ff77287fffcfefbf7cd84abb8172
BLAKE2b-256 checksum
How to use checksums
e382d2eb15646a0389b7abc8df13310bc2fad241f43de5892d1c3a54f0b0a14c
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp312-abi3-musllinux_1_2_x86_64.whl

Download URL wse_server-3.0.1-cp312-abi3-musllinux_1_2_x86_64.whl
Size 4.6 MB
Tags CPython 3.12 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
79c83d7b8458d4a2a0f7298b5bd7522ccac9ea4e6d6ae71ffccf59e5e5ad7bb3
BLAKE2b-256 checksum
How to use checksums
495d8733456c5e8e319f7efeb81c2fd10774cf2c4c820f059b20ed89594d6490
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp312-abi3-musllinux_1_2_aarch64.whl

Download URL wse_server-3.0.1-cp312-abi3-musllinux_1_2_aarch64.whl
Size 4.3 MB
Tags CPython 3.12 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
820f7493f60ad6cfb6421886eef6b80c5a279eb36c5d3773172570d37689e14e
BLAKE2b-256 checksum
How to use checksums
4e994f927eb00a2740a7a5f14396b296f943b8f78a124ece91001687f54f2152
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp312-abi3-manylinux_2_28_aarch64.whl

Download URL wse_server-3.0.1-cp312-abi3-manylinux_2_28_aarch64.whl
Size 4.2 MB
Tags CPython 3.12 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
27612630fd9ca7c0e8ff3a6cb756e086146b9dbf215204e1cd2be7789630000c
BLAKE2b-256 checksum
How to use checksums
aac94c5fa6a8c419fbdd32be6a54f5c5c8317d21fc3c33fc5cc8f5c842788a4f
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL wse_server-3.0.1-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 4.4 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
8e3688db3b7c63d9a973cec02f329b717278f000840097a8f530b8316f6ab67d
BLAKE2b-256 checksum
How to use checksums
9a085223f156b8dbd2fc3df6031982d8d2cba2aab42f1a0795b76c273e6887df
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp312-abi3-macosx_11_0_arm64.whl

Download URL wse_server-3.0.1-cp312-abi3-macosx_11_0_arm64.whl
Size 3.9 MB
Tags CPython 3.12 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
601708eb9d9107df486730f411aee17a7f0eb75abf02430daf02dc90b94ccd52
BLAKE2b-256 checksum
How to use checksums
73b8f828441c72beab3e0a22a98c2ad4f334dbc88ce21d24a11b03f0db11a78b
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 15, 2026.

Transparency log

Release files / wse_server-3.0.1-cp312-abi3-macosx_10_12_x86_64.whl

Download URL wse_server-3.0.1-cp312-abi3-macosx_10_12_x86_64.whl
Size 4.3 MB
Tags CPython 3.12 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
3d00e783f34641830e1caedd780644a0809bb9598ef5b288b75b2c0c94ae5f92
BLAKE2b-256 checksum
How to use checksums
d99a966047aadb009a4147759199dfe9c0b1f84fd831532ed2693be73031d3c5
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 15, 2026.

Transparency log

Security for wse-server 3.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 21 files in this release have been uploaded with provenance metadata.

Select from 21 files

Attestation for wse_server-3.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 Nov 15, 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.

Release history Release notifications | RSS feed

This release

3.0.1 This release

21 release files Full provenance

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