Skip to main content

WSE

PyPI - Server PyPI - Client npm crates.io - Server crates.io - Client pub.dev Maven Central 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 the connection, its subscriptions and recovery, on a page without a framework or with React, Vue or Svelte; React Native apps use it too. Interfaces written in Rust (Leptos, Yew, Dioxus) use the Rust client compiled to WebAssembly. iOS, Android and Flutter apps, on phones and on desktops, use the Rust client through its Swift, Kotlin and Dart packages. Services and bots connect with the Python or the Rust client.

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. Where every fact counts, the TypeScript, Swift, Kotlin and Dart clients hold a topic after a reconnect until the application has reloaded its state, and recover from what it committed it applied.
  • 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: without a framework, React, Vue, Svelte; React Native apps
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
wse_client flutter pub add wse_client Flutter and Dart apps (Android, iOS, macOS, Linux, Windows)
wse-swift Swift Package Manager: https://github.com/silvermpx/wse-swift iOS and macOS apps
wse-client-android implementation("io.github.silvermpx:wse-client-android:3.1.0") Android apps

A server in Python

pip install wse-server
import json
import threading
import time

from wse_server import RustWSEServer

server = RustWSEServer("0.0.0.0", 5007, jwt_secret=b"replace-with-a-strong-secret-key!")
server.enable_drain_mode()
server.start()
print("token:", server.issue_token("user-1"))


def handle_events():
    while server.is_running():
        for kind, conn_id, data in server.drain_inbound(256, 50):
            if kind == "auth_connect":  # data: the user id from the token
                server.subscribe_connection(conn_id, ["prices"])
            elif kind == "msg":  # data: the client's message, a dict
                print(conn_id, data)


threading.Thread(target=handle_events, daemon=True).start()

price = 100.0
while True:
    price += 0.25
    server.broadcast("prices", json.dumps({"t": "price", "p": {"symbol": "ACME", "price": price}}))
    time.sleep(1)

Clients connect to ws://localhost:5007/wse with the printed token: a browser sends it as the access_token cookie, other clients in the Authorization: Bearer header. Messages are JSON objects with their type in t and their data in p. The rest of the Python API is further down, and runnable examples are in examples/.

A server in Rust

cargo add wse serde_json tokio --features tokio/full
use wse::{Config, Connect, Handler, Inbound, JwtSettings, Server, Subscribe};

/// Every connection joins its user's topic.
struct App;

impl Handler for App {
    type Connection = String;

    fn connect(&self, connect: &Connect<'_>) -> Option<String> {
        let user = connect.user_id?.to_owned();
        connect.subscribe(vec![format!("user:{user}")], &Subscribe::default()).ok()?;
        Some(user)
    }

    fn message(&self, user: &mut String, message: Inbound, _size: usize) -> bool {
        if let Inbound::Json(message) = message {
            println!("{user}: {message}");
        }
        true
    }

    fn signed(&self, _user: &mut String, _message: serde_json::Value, _size: usize) -> bool {
        false
    }

    fn disconnect(&self, _user: String) {}
}

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let mut config = Config::default();
    config.jwt = Some(JwtSettings::new(std::env::var("JWT_SECRET")?));
    let server = Server::new(config)?;
    server.start(tokio::net::TcpListener::bind("0.0.0.0:5007").await?, App)?;

    let publisher = server.publisher();
    publisher.publish("user:42", r#"{"t":"order_filled","p":{"id":7}}"#)?;
    publisher.send_to_user("42", r#"{"t":"notice","p":{"text":"hello"}}"#)?;

    tokio::signal::ctrl_c().await?;
    server.stop().await;
    Ok(())
}

The server runs on the application's own tokio runtime. The Handler hears connections and their messages; the Publisher sends to topics, to single connections and to every connection of a user. A complete chat room is in crates/wse/examples/chat.rs, and the crate's own README has the rest.

Clients

TypeScript and React

npm install wse-client
import { useMemo, useState } from 'react';
import { useWSE, type UseWSEConfig } from 'wse-client';

export function Price() {
  const [price, setPrice] = useState<number>();
  const config = useMemo<UseWSEConfig>(() => ({
    endpoints: ['wss://example.com/wse'],
    registerHandlers: (processor) => {
      processor.registerHandler('price', (msg) => setPrice(msg.p.price));
    },
  }), []);
  const { connectionHealth } = useWSE('cookie', ['prices'], config);

  return <p>{connectionHealth}: {price ?? '-'}</p>;
}

A browser cannot put headers on a WebSocket, so it signs in with the cookie your login endpoint sets (access_token); 'cookie' tells the hook to connect. Every useWSE() on a page shares one connection. Without React, createWSEClient from wse-client/core makes a client of its own, which wse-client/react, wse-client/vue and wse-client/svelte hand to components and wse-client/react-native sets up for an app. More in the TypeScript client's README.

Python

pip install wse-client
import asyncio

from wse_client import connect


async def main():
    async with connect("ws://localhost:5007/wse", token="<token>", topics=["prices"]) as client:
        async for event in client:
            print(event.type, event.payload)


asyncio.run(main())

SyncWSEClient does the same without asyncio. More in the Python client's README.

Rust

cargo add wse-client tokio --features tokio/full
#[tokio::main]
async fn main() -> Result<(), wse_client::Error> {
    let mut config = wse_client::Config::new("ws://localhost:5007/wse");
    config.token = Some("<token>".into());
    config.topics = vec!["prices".into()];
    let (_client, mut events) = wse_client::connect(config).await?;
    while let Some(incoming) = events.next().await {
        println!("{incoming:?}");
    }
    Ok(())
}

The same crate builds for the browser (wasm32-unknown-unknown), for Leptos, Yew or Dioxus apps, with the same API. A Handler can read each message straight from its frame into your own types, without copying it. More in the Rust client's README.

Swift, Kotlin and Flutter

iOS, Android and Flutter apps use the Rust client through packages of their own: the same reconnects, recovery, end-to-end encryption and signed messages, with async calls and the events as a stream, and helpers that pause the connection while the app is in the background or offline.

let client = try await WseClient.connect(
    WseConfig(url: "wss://example.com/wse", token: token, topics: ["prices"]))
for try await item in client.events() {
    if case let .message(message) = item { print(message.kind, message.json ?? "") }
}
val client = connectClient(WseConfig(url = "wss://example.com/wse", token = token, topics = listOf("prices")))
client.events().asFlow().collect { item ->
    if (item is WseItem.Message) println("${item.message.kind}: ${item.message.json}")
}
final client = await WseClient.connect(
  wseConfig('wss://example.com/wse', token: token, topics: ['prices']),
);
await for (final item in client.events()) {
  if (item.kind == WseItemKind.message) print('${item.name}: ${item.json}');
}

More in the READMEs of the Swift, Kotlin and Dart packages.

The Python server

Everything here is a method or an option of RustWSEServer. The integration guide has the complete reference.

Options

Sizes are in bytes, times in seconds.

Option Default
host, port required The address to listen on
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.1.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.1.0
File Size Uploaded Provenance Actions
wse_server-3.1.0.tar.gz 337.4 kB With provenance Details for wse_server-3.1.0.tar.gz

Built distributions (wheels)

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

Total release size: 84.4 MB

Release files / wse_server-3.1.0.tar.gz

Download URL wse_server-3.1.0.tar.gz
Size 337.4 kB
Tags Source
SHA-256 checksum
How to use checksums
449543872d5b3f5adca00b4ba05eefaef7f029a89b35f5577f44801a5d0187c8
BLAKE2b-256 checksum
How to use checksums
86fce40b238bd063119524af46f18fe820b630b26117028a3cdc950eb16d21d3
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
830353cec4738621fe800f9a9cda4d186dd3d981553bb3d5f536b6878a78491c
BLAKE2b-256 checksum
How to use checksums
2007aee0e3e8349b3013acb349ec8e62fbd4b91697618d08f346b1a4038b0c05
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
4059f882daa245771b6b285de184c2ebff00916d7ec9d171b18d68e212b55241
BLAKE2b-256 checksum
How to use checksums
57dbd0f346dd8e290cf78b8f21c7aabdbd2db28a7320972184a958a11283d1d2
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
6021c2dfb7ca56fa69c193a07418b359fdffc3ba6bc634cac97112d41e4e67ab
BLAKE2b-256 checksum
How to use checksums
84a2c955d2797890596629d587cd7bf559b4d9fbf234f81a67eb90db09dd2930
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
0648aaf528ef1a51d883fbd3c14a049b5aa4cd1fbcc12207e61604fb25bb57da
BLAKE2b-256 checksum
How to use checksums
c58434e2f8b55dda43bc2ed133ae65b9f3f949389c790a1a47575bb6a3faa787
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.0-cp315-cp315t-macosx_11_0_arm64.whl
Size 4.0 MB
Tags CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
8dab8e879380a580524dee6305f81f1baf823210b00a79e0bece57be97230e3b
BLAKE2b-256 checksum
How to use checksums
6d913a13615fedc1e421363048c2fba1993d8bcc17c57fefca23a7883aa3baf0
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
1a51a4ac81d5e8cf8924e68d27c4d1495c30053b5f2b639568c7e95d7462e78e
BLAKE2b-256 checksum
How to use checksums
3b8e35061c3be7a7739dec49ccfc441e06d5a8f35b624c71520cad62013a1656
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
9de344ec2242aa62aa024c19a20470910a10526bbc099eed0c3b2644bad4740a
BLAKE2b-256 checksum
How to use checksums
73e7b17c9f40866b020ba28b886f03c540f50b9bf517036a13c8964e6f34df26
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
08e48f74914477d8866099f48fc79ae5e42b88bbf242b1dd3a68ca45b877da97
BLAKE2b-256 checksum
How to use checksums
96b71ea1f8ddd355315084439ac9fa75f14f1c6efe14aa0b3912af9cf27cbffe
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
1bafee1fd5d3baf23148e81d5e9f591ce6b082f9f790243136eb6a80666651ce
BLAKE2b-256 checksum
How to use checksums
661e5d1dcfc4f5c596d36353bfb4affb0d8a49cc40169211f217b66eb2bb27df
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
5830ed2341506355bc51e172d1a2b63c0704fd31c1f9c067f7c6d33421f98ab5
BLAKE2b-256 checksum
How to use checksums
631d03bafa4e400ad08af599bbd4ddd1ca3c476f218356cdc43123bcc47869b7
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.0-cp314-cp314t-macosx_11_0_arm64.whl
Size 4.0 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
198e7e3ae0440eb40f0fcf45a07bc937ab8613f7e11542eea72053919c226e48
BLAKE2b-256 checksum
How to use checksums
a4d817b8a9995e679935e92b63da6cdacd9c7e043041b7af157ac24461432592
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
a5cee6bcc48adace95da45347c6cce6cc51789fb340585a15e598a90018b204e
BLAKE2b-256 checksum
How to use checksums
003f49a21c8cbcda118e454e2b05a89689985fe8399c1b47549e08c0c3703d5a
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.0-cp312-abi3-win_arm64.whl
Size 4.0 MB
Tags CPython 3.12 Windows ARM64 abi3
SHA-256 checksum
How to use checksums
104398a6d19f83bd50f93b54e3a112c76983499a8647d5be490555377ba6a8ff
BLAKE2b-256 checksum
How to use checksums
a725f7120e7510124783547ed32f6c7f2bd046cdb7cf47adff27f060e6c1d3a5
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
2b10e104a79be6324901c34617985f9d87543abc9219bcc01e3420a7bfff286b
BLAKE2b-256 checksum
How to use checksums
68db99766a87e30fdb974893f713d6e89b9ddd66d87af6155703ac8843286b09
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.0-cp312-abi3-musllinux_1_2_x86_64.whl
Size 4.7 MB
Tags CPython 3.12 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
47c5c4741d87979123d5c07cfa371aa0ee08af45245f702685f699a804720fbb
BLAKE2b-256 checksum
How to use checksums
94fb0d7d26700b2d0eaf569986a7c2175fabfd3d5f793f95d38efcc0322b75e5
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
720a86232ebf06d48be8c600315f9534341b1bd0c46d1c6a35ca5863e67919c3
BLAKE2b-256 checksum
How to use checksums
60efab29cf22ed5b9eeb56ee99acc0433e85643f5414b95a6eae778791c68493
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
e89167c7c33b7196ebe26ae1fe9a742d2826f6103be304f7fa3778c561fa4bf0
BLAKE2b-256 checksum
How to use checksums
14116b5fec88a362afae6d64302c3c5cf02d2f48aeeed20c547e166fe935a631
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
f2e00178372209268fba780ae8cb8da2f17a8b647f46e05c1e5337d65ccf729a
BLAKE2b-256 checksum
How to use checksums
593027fe6baf207159072d2a66c3463c2111bc0811d494f4dabdad6e882d0cc0
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.0-cp312-abi3-macosx_11_0_arm64.whl
Size 4.0 MB
Tags CPython 3.12 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
bb7369d5dc763de017ed641668a83ebb78a78b77e2da01046393b56330bb3e87
BLAKE2b-256 checksum
How to use checksums
4c23dc22ab8832d68b51f1f85488bdb8c7f457ac3f006d2639ee81ff718d4c72
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 16, 2026.

Transparency log

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

Download URL wse_server-3.1.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
12f7a32839240314cffa520757ce785483944540ff3261b3a082a06579317a04
BLAKE2b-256 checksum
How to use checksums
55309f193f8ac49dfef143c42304e298865293a68cd8903a24f7b1f033bb4262
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 16, 2026.

Transparency log

Security for wse-server 3.1.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.1.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 16, 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.1.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