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

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.0
File Size Uploaded Provenance Actions
wse_server-3.0.0.tar.gz 321.9 kB With provenance Details for wse_server-3.0.0.tar.gz

Built distributions (wheels)

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

Total release size: 83.8 MB

Release files / wse_server-3.0.0.tar.gz

Download URL wse_server-3.0.0.tar.gz
Size 321.9 kB
Tags Source
SHA-256 checksum
How to use checksums
e5cecd55186d765cc5ff3114ccb33e03767868fc1630755becc8b5bdfdb0dcbe
BLAKE2b-256 checksum
How to use checksums
399f09539bf7049e1ee06eb3f232317e6258223428d458d16da975fcdee0b2ba
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.0-cp315-cp315t-win_arm64.whl

Download URL wse_server-3.0.0-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
5746625cb2fbee4bc352c16bf0f7b563c950e0eb8d96046dd1330737dbf03874
BLAKE2b-256 checksum
How to use checksums
220b61bc63023742bf3f87cd6e486c4eed24afeee131791f7624390b2e40714c
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.0-cp315-cp315t-win_amd64.whl

Download URL wse_server-3.0.0-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
edf68aa640a1cb2ea6f05c5530e80a14a56d419bf5325cd40d655eb5b4f0c908
BLAKE2b-256 checksum
How to use checksums
3c268c3e98d01e6bed38fe2b71b22db3d6394d7ff0f6c4851397b9597cf2f09d
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.0-cp315-cp315t-manylinux_2_28_aarch64.whl

Download URL wse_server-3.0.0-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
a071e36aab31ecfbec2126c370245548c660e26bb945f092d73d915c0eea83db
BLAKE2b-256 checksum
How to use checksums
c759b1ba9438db2bff23b1a72739b8f18a981011dfb58bb22b063b15b247677a
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.0-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL wse_server-3.0.0-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
667d399d018b9f996ed21cd15a5b4093387fccaf0f7aae3e8f614c0b3a4abe5a
BLAKE2b-256 checksum
How to use checksums
09a5a98bb57fc1edf8c6b64ee87915f5b3e1576116af7c488740e4e58d55e32c
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.0-cp315-cp315t-macosx_11_0_arm64.whl

Download URL wse_server-3.0.0-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
fdba9bbc1657ebe6ae0e6abe67cdfd5c0266b3b04f98cbd6a327626b509a2912
BLAKE2b-256 checksum
How to use checksums
7c1216f818e9638a84a700afe31d2412bab85f451352113dac58c55ec12b193f
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.0-cp315-cp315t-macosx_10_12_x86_64.whl

Download URL wse_server-3.0.0-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
e932c013394a05d72552d881976f2d4934232ec054fe0e3e2709bdd1c31f6f4d
BLAKE2b-256 checksum
How to use checksums
4eb40e0bef23ec33f4a2e265f4ee31f1c418b65d24cc90c8471e7fdbde0897bf
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.0-cp314-cp314t-win_arm64.whl

Download URL wse_server-3.0.0-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
e666e2bdf919f3a299e131637715c65f7b665552166625f56740538f94625a94
BLAKE2b-256 checksum
How to use checksums
ef33138edddb21fcd85ae9be54aa2326b925b6a87317f9e791303f566d02ba94
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.0-cp314-cp314t-win_amd64.whl

Download URL wse_server-3.0.0-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
81105c9680c725b78dee762dcfb38eaf0e9eea5c26baa9d8fa971e65503b1080
BLAKE2b-256 checksum
How to use checksums
dc2563580e7d5ec3b17021abe25597125954b2dead1411dd020beb98e8e11e42
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.0-cp314-cp314t-manylinux_2_28_aarch64.whl

Download URL wse_server-3.0.0-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
4dde730fc5a91d141ced77d5d5e5de5479a596cc2a4b47b1a33f414d8ec7ad81
BLAKE2b-256 checksum
How to use checksums
9a37944271981e6bc98617b9a287786a3291f7e2612193822aa2be35d9214da7
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.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL wse_server-3.0.0-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
40f55cc1a29c13fd435ebcf893eeec6e051413e90b3f7b442b90d5508b6d8f44
BLAKE2b-256 checksum
How to use checksums
cee87d5fc8f685c9e515fe91430722925bcfeb691f438bc82dec635a8b897229
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.0-cp314-cp314t-macosx_11_0_arm64.whl

Download URL wse_server-3.0.0-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
a8be17efbabcc80d6254cdcb51190b6571126f3c551200843929c74e640a7723
BLAKE2b-256 checksum
How to use checksums
48d150c7e971d6d82c0f3bb500f1e818987657054b68d6b246c6a13dc471b4b8
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.0-cp314-cp314t-macosx_10_12_x86_64.whl

Download URL wse_server-3.0.0-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
572677ffd2ea66cfa6f903376bf3bf0962a0d56cdf8ff4cda89b6cb206d24ea2
BLAKE2b-256 checksum
How to use checksums
3c082028ebd3ace397eecbb6891ec5ec36d7cb2c40fe200c34d3578b7576d6d1
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.0-cp312-abi3-win_arm64.whl

Download URL wse_server-3.0.0-cp312-abi3-win_arm64.whl
Size 4.0 MB
Tags CPython 3.12 Windows ARM64 abi3
SHA-256 checksum
How to use checksums
8c2cdb2806246cc7b632503c18025c31c2f7b1f6a4e1185f0735922f2f31c606
BLAKE2b-256 checksum
How to use checksums
5304dabe875f12fc863b51c1678e2b34dc705903e15eff25c713db7437b63673
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.0-cp312-abi3-win_amd64.whl

Download URL wse_server-3.0.0-cp312-abi3-win_amd64.whl
Size 4.1 MB
Tags CPython 3.12 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
4fec9d196403e3df97f4c7924a165c35ec0485ff77a03b4e29b508cfcca3f575
BLAKE2b-256 checksum
How to use checksums
db59c02c7553e3208bf0628a9dffedd8cae561536ff36cbd543314ed2550c754
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.0-cp312-abi3-musllinux_1_2_x86_64.whl

Download URL wse_server-3.0.0-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
42efe1ad46a25a0f6d0cc4517e25360e765eab399da989e43448424a9adaefb6
BLAKE2b-256 checksum
How to use checksums
3f02474057ec028080c3b1c5243966c28164ef2de43296fe5f74277db81d5cb5
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.0-cp312-abi3-musllinux_1_2_aarch64.whl

Download URL wse_server-3.0.0-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
347d29c943b42ffa872d837c9c7cc194d5d4f03f094861b8e3c53ecb7025d9cd
BLAKE2b-256 checksum
How to use checksums
82b5aa2cabbabdbc6796435e42e30e36ab1686301fc1551db94597ae257debfd
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.0-cp312-abi3-manylinux_2_28_aarch64.whl

Download URL wse_server-3.0.0-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
14889e287741db5359a62e75b9ff82721bcbe508b16c0a0fa6d85a51c74a4d35
BLAKE2b-256 checksum
How to use checksums
fe6e2ce40acc61d07b7942960a70aaedd81fd9a219151f30bde86f3813fec550
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.0-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL wse_server-3.0.0-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
93255ecba37f70767b89b8d13a368de5b71c1c38fecf0d1071dd7d46d71f563f
BLAKE2b-256 checksum
How to use checksums
318e2858b68cd9d7805d414231e8bfa0f6ed492073cc19a4efa40bdbea77bb50
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.0-cp312-abi3-macosx_11_0_arm64.whl

Download URL wse_server-3.0.0-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
83c4816a9aefe44c8f20e843d35cc61ddfcc843e28e943799f9d525450c92951
BLAKE2b-256 checksum
How to use checksums
af972a14b59802878abd29825b468069c11bcb53e0530d20c4446e5732561121
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.0-cp312-abi3-macosx_10_12_x86_64.whl

Download URL wse_server-3.0.0-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
add42b65cd149f9e5898cb0c6107359e969fa4fbe2d1ae81f8b2c755822c4139
BLAKE2b-256 checksum
How to use checksums
a8c406e3c40f11760796cb38c4a2762cfa48446a669283ddc03ad5382340988a
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.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.

Select from 21 files

Attestation for wse_server-3.0.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 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.0 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