Skip to main content

CrowdyPy

The official Python SDK for Crowded Kingdoms: typed clients for the platform's one GraphQL API (identity, studio administration, world data, ck-exec) and a native UDP replication core.

CrowdyPy follows the CrowdyJS API surface (the same domains, the same two-token model, the same error codes) the way CrowdyCPP does, with Python names (mintAppToken is mint_app_token). Its realtime path is CrowdyCPP's native replication client, bound with nanobind and shipped inside the wheel. Python never touches a datagram.

v0.34.0: a mod knows the Studio revision it runs. client.exec.mod_build and mod_client_build take the Studio project and saved revision a crate is (ExecStudioSource), and the build, the mod version and the CLIENT half deployed from it report them; the Studio controller sends them. client.exec.mod_client_starter is the platform's CLIENT half starter, which a new project's CLIENT target now starts from, and client.crowdy_studio.links() is this tier's Studio origin and wallet page. Vendors CrowdyCPP 0.87.0 and follows CrowdyJS 18.33.0; needs Game API v2.73.0. See MIGRATION.md.

v0.33.0: a voxel's time is its chunk's whole-chunk write. The chunk store dates a copy's voxels by voxelsUpdatedAt (Game API v2.70.0, where an updateChunk or world.set_chunk supersedes older edits), so a chunk-state or LOD write drops no newer change; CachedChunk.row_at orders copies. Vendors CrowdyCPP 0.85.0. Needs ck-api v2.70.0. See MIGRATION.md.

v0.32.0: CrowdyCPP 0.84.0's chunk store. The store merges by the server's time (chunks.confirmed_at): an older change is dropped, a change made while a chunk loads survives the copy, another client's edit goes under your unanswered one, catch_up(since, boxes=None) covers every tracked chunk and merges edits by their time, evict and prune_if prune any view, and hydrate returns whether it applied. After a v0.46.0 server acknowledges the bound control frames, legacy reconnects and releases are dropped. Needs ck-api v2.69.0. See MIGRATION.md.

v0.31.0: hardening from CrowdyCPP 0.83.0. MessagePack keys that are containers are refused (a nested key blew up memory), a NaN serialises as null in place, unchanged keyframes of many actors are not gameplay input, and a legacy reconnect command is paced (legacy_reconnect_window_ms). See MIGRATION.md.

v0.30.0: the ChunkStore rework. ensure_around reads only what is missing, as boxes, paged; set_voxel is paced and returns an edit id, and an edit the server refuses or never echoes is undone (on_edit_refused); a replaced chunk is read again and a reconnect catches up; realtime edits are no longer written back. CrowdyJS 18.30.0 and CrowdyCPP 0.82.0. See MIGRATION.md.

v0.29.0: reconnect commands verify, bound control frames, and chunk_changed. A server's COMMAND_RECONNECT verifies again; against replication servers v0.45.0 the reconnect and release frames carry a per-assignment nonce under their HMAC, so one captured earlier is refused (stats()["stale_bound_control"]); chunk_changed reports a chunk a hub's or mod's world.set_chunk replaced. CrowdyJS 18.29.0 and CrowdyCPP 0.81.0. See MIGRATION.md.

v0.28.0: region reads. chunks.by_distance() and voxels.list_by_distance() take a box (lowChunk, highChunk) as well as a cube, pages are stable and answer the paging applied, since filters a chunk read, voxels.list() pages, and game_apps.nearby_grids() returns your own permissionKeys. Needs ck-api v2.67.0. CrowdyJS 18.28.0 and CrowdyCPP 0.80.0. See MIGRATION.md.

v0.27.0: a replayed idle release cannot end a playing player's session. An idle release that arrives within a minute of this client's own gameplay input reconnects instead of going ConnState.INACTIVE (idle_release_guard_ms, counted in stats()["idle_releases_after_input"]), and a reassignment left over from the session that ended no longer reassigns the next one. The native chunk store keeps unechoed local edits over a stored copy. CrowdyJS 18.27.0 and CrowdyCPP 0.79.0. See MIGRATION.md.

v0.26.0: a new account confirms its email. Since ck-api v2.65.0 a password account made since 2026-11-11 gets no gameplay token until it opens the link auth.register emailed: minting raises EMAIL_CONFIRMATION_REQUIRED, which crowdypy.is_email_confirmation_required_error reads. Tell the player to check their inbox, offer auth.resend_confirmation_email(email), then mint again. Accounts made before then and players an organization manages are not asked. CrowdyJS 18.27.0 and CrowdyCPP 0.78.0. See MIGRATION.md.

v0.25.0: a session released for idleness is final. The replication server ends a session that sends no gameplay input for the app's idle timeout (15 minutes unless the app sets its own idleTimeoutSeconds with apps.update(); 0 turns it off), and the connection moves to ConnState.INACTIVE instead of reconnecting: call client.udp.connect() on the player's next input. It needs ck-api v2.64.0 on the tier. CrowdyJS 18.26.0 and CrowdyCPP 0.77.0. See MIGRATION.md.

v0.24.0: appointed moderators, regions, and the consent refusal's reason. ck-api v2.61.0 refuses a player under 18 SAFETY_MODERATOR_REQUIRED in an app whose organization has appointed no safety moderator (crowdypy.errors.safety_moderator_required_of; apps.app() reads hasSafetyModerator for the organization's members), checks some countries by region (region on an org-managed player's mint and assertion, regionCode on platform.territory_policies()), and says why parental consent cannot be requested: parental_consent_unavailable_of now returns a CrowdyParentalConsentUnavailable with its reason, or None. An age refusal at sign-up stops the same client for 24 hours. It needs ck-api v2.61.0 on the tier. CrowdyJS 18.25.0 and CrowdyCPP 0.76.0. See MIGRATION.md.

v0.23.0: teen safety. ck-api v2.60.0's age, territory and documents gate, and a player's own safety controls. auth.register takes the age screen's birth_date, country and parental_confirmation, auth.record_player_age gives an account its age once, and crowdypy.errors reads the gate's refusals (age_requirement_not_met_of is deliberately a boolean: no refusal names an age). client.safety holds the voice and video scopes, contacts, blocks, a parent's consent and reports; client.moderation is the app's moderators'; apps.recording is what the notice and the indicator show. Org-managed players carry ageYears and country. It also brings CrowdyJS 18.23's Studio game editor (CrowdyStudioController(draft_store=...)). It needs ck-api v2.60.0 on the tier. CrowdyJS 18.24.0 and CrowdyCPP 0.75.0. See MIGRATION.md.

v0.22.0: a deploy's dropped node types. exec.instances returns orphaned, true for an instance whose node type the app's active version no longer deploys: ck-exec 0.19 stops such an instance at once when a deploy or a rollback drops its type, and keeps its saved state. It needs Game API v2.58.0 on the tier. CrowdyJS 18.22.0 and CrowdyCPP 0.74.0. See MIGRATION.md.

v0.21.0: a send waiting across a reassignment is resent then. An actor or voxel update still waiting for its echo when the connection is reassigned is resent as soon as the new session is connected, rather than at its timeout, since its echo went to the session it left. That is its one retry; audio, text and events are never resent. CrowdyJS 18.21.0 and CrowdyCPP 0.73.0. See MIGRATION.md.

v0.20.0: a session's first awaited send is not lost. Every *_and_wait retries the first awaited send of a session once, with a fresh sequence, when it is refused UNAUTHORIZED or, for the echoed actor and voxel updates, when it times out: how a replication server older than v0.42.0 answers a session's first message (v0.42.0 holds it until the session is ready). CrowdyJS 18.20.0 and CrowdyCPP 0.72.0; no API change. See MIGRATION.md.

v0.19.0: a draining instance is left at once. Game API v2.56.0 expires the balancer's affinity cookie on a draining instance's responses; CrowdyPy forgets the expired cookie, so the next request lands on an instance that is staying. CrowdyJS 18.19.0 and CrowdyCPP 0.71.0; no API change. See MIGRATION.md.

v0.18.0: text chat and direct-message keys, and the recording switch. Game API v2.55.0 adds the app-level use_text_chat and use_direct_messages keys: without them the realtime servers refuse a player's text, channel text and direct messages with UNAUTHORIZED. A tier that grants access gets both unless applyCommunicationDefaults is false, and replayLoggingRecordsMedia leaves voice and video out of an app's recording. Deleting a managed player now erases its content, and a legal hold refuses it with LEGAL_HOLD. See MIGRATION.md.

v0.17.0: the Org-Managed Players Addendum. ck-api v2.53.0 serves org-managed players on every tier, once an admin of the organization has accepted the addendum in Studio; until then its sign-ins and refreshes answer ORG_LEGAL_ACCEPTANCE_REQUIRED, which crowdypy.errors.org_legal_acceptance_required_of reads, and client.managed_players.settings(org_id) says where the organization stands. CrowdyJS 18.17.0 and CrowdyCPP 0.69.0. See MIGRATION.md.

v0.16.0: org-managed players. An organization that runs its own accounts signs its players in itself: its server mints a player's app token with an org token, or its sign-in service signs an assertion. A device holds the first with client.portal.adopt_app_token(response) (it refuses an org token, which stays on the organization's server; there is no org-token mint wrapper) or trades the second with client.portal.exchange_managed_player_assertion(app_id, assertion), and gives the result to client.set_app_token. client.managed_players is the organization's administration. CrowdyJS 18.16.0 and CrowdyCPP 0.68.0. See MIGRATION.md.

v0.15.0: a voxel edit that waits for the server, and opcode 140 from client.udp. chunks.set_voxel(..., optimistic=False) changes nothing locally until the server's echo of the edit arrives; client.udp.send_generic_spatial sends an app-defined spatial message. CrowdyJS 18.15.0 and CrowdyCPP 0.67.4. See MIGRATION.md.

v0.14.2: CrowdyJS 18.14.0 and CrowdyCPP 0.67.3. player_wallet.charges() is deprecated: read transactions(), whose usage_debit entries are the usage charges.

v0.14.1: the exec socket names a paused app and a switched-off app or type. AppPaused, AppDisabled, and TypeDisabled. Still CrowdyJS 18.13.0 and CrowdyCPP 0.66.0.

v0.14.0: the economy (CrowdyJS 18.13.0, CrowdyCPP 0.66.0). kit.player, the caller's own player hub, and its views kit.inventory, kit.wallet, kit.progression, kit.achievements, kit.quests, kit.crafting, kit.loot and kit.production; markets by name: kit.shops.at(key), kit.market.at(key) and kit.trades.at(key). It lives in hub state and is not a ledger. A change refused unavailable is sent again with its action id. They need ckx-sdk 0.12.1 in the tier's compute toolchain (dev: v1.15.0).

v0.13.0: the genre starters (CrowdyJS 18.12.0, CrowdyCPP 0.65.0). Nine more kit modules, one per ck-exec genre starter: kit.leaderboards.board(name), kit.tables.table(key) (the caller's hand as private state), kit.tactics.battle(key), kit.encounters.encounter(key), kit.minigames.duel(key), kit.instances.run(key), kit.arenas.arena(key), kit.racing.race(key) / ball(key) and kit.territory.map(key) / zone(key), in both clients. They need a compute toolchain with ckx-sdk 0.11.0 on the tier.

v0.12.0: the Game Kit on ck-exec (CrowdyJS 18.11.0, CrowdyCPP 0.64.0). client.kit(app_id) gains typed clients for the ck-exec starter hubs, the client half of the game kit whose server half is ckx_sdk::kit: kit.world (conditions and resource nodes mirrored, harvests, liveops for developers), kit.matchmaking.queue(name) (parties matched whole), kit.sessions.open(key) (lobby to result), kit.npcs.area(key) (mobs, NPCs, players' pets), kit.topology (compose, check, build and deploy the starters), and kit.spectate, kit.emotes and kit.shards. They share one exec connection (kit.runtime) that paces calls under the gateway's limit, resends only what is safe and mirrors topics with resync on gaps, epochs and reconnects; a hub's refusal is a KitError with its code. Both clients have it: the blocking one runs a mirror's resync beside the connection's reader thread. Exec reconnects wait with jitter. See MIGRATION.md.

v0.11.0: access that ends ends for good, and channel and team bans (CrowdyJS 18.10.0, CrowdyCPP 0.63.0). A host's 4403 close (ck-exec 0.16: the player was suspended, revoked, signed out or blocked) is final: ExecConnection.on_access_ended hears the reason, the call in flight fails Denied, and the connection does not redial. client.channels.ban / unban and client.teams.ban / unban manage bans, and account_blocked_of / group_member_banned_of read the two refusals. See MIGRATION.md.

v0.10.0: the input log says what it lost (CrowdyJS 18.9.0, CrowdyCPP 0.62.0). Every session from client.input_log.sessions carries missingRecords, the inputs the replication server accepted that never reached the log, which needs the Game API release after v2.40.2. Its docstrings name the new end reasons (paused among them), the two read refusals worth retrying with the same cursor, and how to stop a read nobody will see: cancel its task, which closes the request and frees its server read share. See MIGRATION.md.

v0.9.1: the input log's session filter sends userId as a string, and its reads document when to retry. See the 0.9.1 bullet below; 0.9.0 added the SDK a build compiled against.

v0.8.0: voice, channel audio, wide voxels, and pause and access refusals (CrowdyJS 18.7.0, CrowdyCPP 0.60.0).

  • Voice: crowdypy.media's voice helpers (an optional 10-byte header per codec frame, VoicePacketizer, VoiceJitterBuffer), and client.udp.send_channel_audio() with the channel_audio handler, which reaches every member of a channel wherever they are (party and guild voice).
  • World Stores: ChunkStore keeps voxel edits the 16x16x16 one-byte grid cannot hold in an overlay, and applies the echo of your own edit once. session.on("voxel_update") and session.on("generic_spatial") reach a game that keeps its own world.
  • Refusals: crowdypy.is_app_paused() reads the runtime gate that tokens and the bootstrap carry, and app_paused_of, access_refusal_of and actor_exists_of read the new refusals.
  • New calls: users.player_profile(s), app_access.suspend and unsuspend, and exec.restart_type.
  • 0.9.0: every build (exec.build, build_status, wait_for_build and the mod builds) carries sdk_version, the ckx-sdk (CLIENT half: crowdy-client-sdk) version the platform compiled it against, whatever the crate names. It needs ck-api v2.40.2, since the build documents select it.
  • 0.8.0 needs the ck-api release after v2.39.0, since the token mutations select runtimeGate. Channel audio and the voxel echo need replication server v0.37.0.
  • 0.7.0 brought the input log (client.input_log.sessions() and messages(), and replayLoggingEnabled). 0.6.0 brought distance-limited channel messages (udp.send_ranged_channel_message()) and the terms gate (auth.record_player_consents()).
  • 0.5.1 made ChunkStore.hydrate() keep every recorded voxel edit (voxelStates) and ensure_around() keep a chunk it already loaded.
  • 0.5.0 brought the ck-exec gateway check (client.exec.connect() sends the connect token only to a gateway on the game API's estate, and reports a refusal as Denied) and open grids (game_apps.open_permissions() and set_open_permissions()).
  • 0.4 brought the headless Crowdy Studio (crowdypy.studio), player-host observation (crowdypy.player_host), the roots CrowdyCPP covers beyond CrowdyJS, and the strict parity gate (docs/parity-matrix.md has no gaps); 0.3.0 the World Stores, the Game Kit, ck-exec and subscriptions; 0.2.0 native UDP replication (client.udp); 0.1.0 the GraphQL client.

See MIGRATION.md.

Install

pip install crowdypy

Wheels: CPython 3.12+ (one abi3 wheel per platform) and free-threaded CPython 3.14, on Linux x86_64 / aarch64, macOS arm64 / x86_64 and Windows x64. OpenSSL is linked statically; nothing else native is needed. docs/compatibility.md has the details, including the tier versions below.

Each tier of the platform has its own release line, and a build defaults to its own tier's API origin (crowdypy.CROWDY_DEFAULT_TIER says which):

Tier PyPI version Pin
dev X.Y.Z.devN crowdypy==0.4.0.dev1
test X.Y.ZrcN crowdypy==0.4.0rc1
prod X.Y.Z crowdypy==0.4.0

pip skips pre-releases unless a requirement names one, so a prod range never picks up a dev or test build. The same wheels and the sdist are attached to each GitHub release, and pip installs one from its URL (pip install https://github.com/CrowdedKingdoms/CrowdyPy/releases/download/<tag>/<wheel>).

Quick start

import asyncio

import crowdypy

API = "https://ck.dev.crowdedkingdoms.com"


async def main() -> None:
    # The identity client: sign-in, account and studio calls, minting.
    async with crowdypy.AsyncCrowdyClient(http_url=API) as identity:
        await identity.auth.login("player@example.com", "correct-horse-battery")
        minted = await identity.portal.mint_app_token("42")

    # The game client: one per app, at the app's own datacenter.
    async with crowdypy.AsyncCrowdyClient(
        http_url=minted.game_api_url or API, discovery_url=minted.discovery_url
    ) as game:
        game.set_app_token(minted)
        print(await game.server_status.server_with_least_clients())


asyncio.run(main())

Without an event loop, crowdypy.sync.CrowdyClient has the same methods, without await:

from crowdypy.sync import CrowdyClient

with CrowdyClient(http_url=API) as identity:
    identity.auth.login("player@example.com", "correct-horse-battery")
    print(identity.users.me())

Two tokens, two clients

There is one API origin but two tokens, as in every Crowded Kingdoms SDK:

  1. Sign-in (auth.login, a magic link, or social/OIDC) yields an identity session token: account, studio administration and minting. It is not accepted for gameplay.
  2. Gameplay needs a short-lived app-scoped token per app (portal.mint_app_token(app_id)), which is also the HMAC key for native UDP. Refresh it with client.refresh_gameplay_token() (concurrent callers share one refresh). It is refused with LEGAL_ACCEPTANCE_REQUIRED until the player's agreement to the legal documents and age attestation are stored: show both checkboxes, then call auth.record_player_consents(accept_legal=True, attest_age_of_majority=True). With an app's own documents (auth.app_required_documents(app_id)), pass its app_id too.
  3. Build one identity client and one client per game. The game client points at the app's datacenter (game_api_url) with discovery_url set, so it can find the app again if that instance stops answering.

Persist them the same way: FileTokenStore.session_path(directory, api_origin) names the session file (one per origin, shared by every game) and FileTokenStore.app_path(directory, app_id) the gameplay one (one per app):

from crowdypy import FileTokenStore

identity = crowdypy.AsyncCrowdyClient(
    http_url=API, token_store=FileTokenStore(FileTokenStore.session_path(state_dir, API))
)

CrowdyPy sends no Origin header, so direct sign-in is served to it; hosted browser sign-in (portal.signIn in CrowdyJS) is a browser flow and is not part of this SDK.

Errors

Every error is a crowdypy.CrowdyError. A GraphQL refusal is a CrowdyGraphQLError with the server's stable code (error.code == "FORBIDDEN") and extensions; HTTP, network and timeout failures have their own classes. CrowdyAppUnavailableError (the app's datacenter is not serving) and CrowdyUserCodeFaultError (a player module faulted; player_fault_of(error) reads the fault) mirror CrowdyJS. A WRONG_DATACENTER refusal moves the client to the app's datacenter and retries once, by itself.

A paused app (its organization ran out of funds, hit a spend cap, or let a subscription lapse) still mints a token, so check crowdypy.is_app_paused(minted.runtime_gate) before entering the world, and tell the player it is paused. Replication then refuses sends with UDP error 33 (APP_PAUSED). crowdypy.app_paused_of(error), access_refusal_of(error) (ACCESS_REVOKED, ACCESS_SUSPENDED with suspended_until, ACCESS_NOT_GRANTED) and actor_exists_of(error) read those refusals. None of them clears by retrying.

Every mint and refresh passes the player gate (ck-api v2.60.0), and its refusals have readers too: territory_not_supported_of (with the country), age_required_of (give the age with auth.record_player_age), age_requirement_not_met_of (a boolean: no refusal names an age), legal_acceptance_required_of (with the missing_documents), safety_log_required_of and safety_moderator_required_of (ck-api v2.61.0). client.safety answers social_limit_reached_of and parental_consent_unavailable_of (with the reason). After an age refusal at sign-up or at record_player_age, the same client is refused both for 24 hours whatever it sends: do not ask again.

Player safety

client.safety is the player's own controls in one app, on the game client (the app token): voice and video scopes (comm_settings, set_comm_settings; a player can only lower them), contacts (request_contact, accept_contact, remove_contact, contacts, contact_requests), blocks (block, unblock, blocks), a parent's consent for a player under 18 (request_parental_consent) and reports to the app's moderators (file_report). The platform enforces all of it on the realtime servers. When apps.recording(app_id) says voice or video is recorded, show the player your notice and indicator. An app's moderators (moderate_safety) read and decide reports with client.moderation.

Replication

minted = await identity.portal.mint_app_token("42")
async with crowdypy.AsyncCrowdyClient(
    http_url=minted.game_api_url or API, discovery_url=minted.discovery_url
) as game:
    await game.udp.connect(minted)  # assign a server, open the socket
    game.udp.subscribe({"actor_update": lambda n: print(n.uuid, n.chunk, n.payload)})
    await game.udp.send_actor_update((0, 0, 0), my_uuid, pose_bytes)
    echo = await game.udp.send_actor_update_and_wait((0, 0, 0), my_uuid, pose_bytes)

For a game loop, use the connection underneath: send a frame's entities in one call, and read whole batches.

conn = game.udp.connection
conn.send_actor_updates(chunks, uuids, poses, stride=88)  # numpy (n, 3) int64, n x 32 octets
async for batch in conn.batches():
    actors = batch.types == crowdypy.wire.MessageType.ACTOR_UPDATE_NOTIFICATION
    positions = batch.chunks[actors]  # a view, not a copy

crowdypy.replication.ReplicationConnection is the same for code without an event loop: wait() and then poll() from your own loop.

Voxel positions and types are the app's signed 16-bit values, and a voxel state is at most 1,024 bytes (InvalidArgument otherwise, nothing sent). Replication server v0.37.0 echoes every accepted voxel edit back to its sender as a voxel_update.

Voice

send_audio_packet reaches players near a chunk and carries whatever bytes it is given; a game with a voice format of its own keeps it. The voice helpers in crowdypy.media are an optional format that every Crowded Kingdoms SDK shares, byte for byte. Each packet is a 10-byte header (version 1, the codec, a u16 seq, a u32 timestamp in codec samples, the frame's duration and two talk-spurt flags) followed by one codec frame. VoicePacketizer numbers one sender's frames. VoiceJitterBuffer puts each sender's packets back in order and plays them out 60 ms after the first packet of a talk spurt arrived. It reports a frame that never came as a gap, drops one that arrives after its playout time, and holds at most 64 frames a sender.

send_channel_audio reaches every member of a channel wherever they are (party or guild voice), at most 1,024 bytes a packet. The sender needs the channel's send_voice (members_can_speak=True on creation gives it to the member role) and the player's use_voice_chat. There is no echo, and members receive channel_audio:

from crowdypy.media import VoiceCodec, VoiceJitterBuffer, VoicePacketizer

party = VoicePacketizer(VoiceCodec.OPUS, 20)
# Every 20 ms while the player talks (`opus_frame` from your own encoder):
await game.udp.send_channel_audio(channel_id, my_uuid, party.packetize(opus_frame, last=released))
# ...and party.skip() for every 20 ms of silence that is not sent.

voices = VoiceJitterBuffer()
game.udp.subscribe({"channel_audio": lambda n: voices.push(f"{n.channel_id}:{n.uuid}", n.payload)})
for slot in voices.poll():  # at least once a frame, from your audio clock
    if slot.gap:
        conceal(slot.key, slot.frame_ms)  # the frame never came
    else:
        play(slot.key, slot.codec, slot.frame)

No codec ships with CrowdyPy, and the wheel links none: which codec an app uses (Opus, or G.711 µ-law where it has no Opus), and the library that encodes and decodes it, is the app's choice. Where a voice sits in the world (panning, distance attenuation) is the game's too.

World Stores

from crowdypy.codecs import f32, struct_codec, u16
from crowdypy.stores import create_world_session

pose = struct_codec({"x": f32(), "y": f32(), "z": f32(), "yaw": u16()})
session = create_world_session(game, app_id, actor_codec=pose, host=True, save=True)
session.self.join((0, 0, 0), {"x": 0.0, "y": 64.0, "z": 0.0, "yaw": 0})
session.actors.on_join(lambda actor: print("joined", actor.uuid, actor.value))
asyncio.create_task(session.run())  # tick 60 times a second

snapshot = session.actors.snapshot()  # once a frame: every actor at once
states = pose.decode_many(snapshot.state_offsets, snapshot.state_data)  # numpy, no loop

session.chunks is a helper for 16x16x16 chunks with one byte per voxel. An edit that grid cannot hold (a type outside 0-255, a position outside 0-15) is kept in the chunk's overlay(), and voxel_type_at reads it first. The echo of your own set_voxel is not applied a second time; with optimistic=False the edit is applied only when that echo arrives, and nothing is queued for write-back. A game with other addressing reads every edit from session.on("voxel_update", ...), which includes those echoes.

Game Kit

client.kit(app_id) drives the ck-exec starter hubs (the server half is ckx_sdk::kit), with the same modules as CrowdyJS's client.kit(appId):

kit = game.kit(app_id)
await kit.world.conditions.start()  # mirrored: time of day, weather, liveops modifiers
queue = kit.matchmaking.queue("ranked")
queue.on_matched(lambda session: print("matched into", session))
await queue.join(1200)
watching = asyncio.create_task(queue.watch())  # asks while the player waits
try:
    await kit.npcs.area_at(12, -3).attack(4)
except KitError as e:
    if e.code == "cooldown":
        ...

kit.world, kit.matchmaking, kit.sessions, kit.npcs and kit.topology (compose, check, build and deploy the starters) share one exec connection (kit.runtime): it paces calls under the gateway's 120 per 10 s, sends a call again only when that is safe (it did not run, or it carries an action_id the hub answers once), and its mirrors (HubState, CollectionMirror, PrivateState) take a new snapshot after a gap, another epoch or a reconnect. kit.spectate, kit.emotes and kit.shards are the client conventions, and kit.social the parties, guilds and chat rooms. The blocking client's kit is the same, with blocking calls.

Crowdy Studio

from crowdypy.studio import CrowdyStudioController

studio = CrowdyStudioController.for_client(game, app_id=app_id, grid_id=grid_id)
await studio.initialize()  # opens the first project
studio.update_file("SERVER", "src/lib.rs", source)  # autosaves
result = await studio.test_draft()  # build, deploy and switch on the mod
print(result.status, studio.get_state().build_output)

A CLIENT target runs in a host you pass as broker_factory; the browser Studio runs it in a Web Worker. A bound Construct game opens its repository draft instead of the mod crates when you pass draft_store=, a factory returning the project's crowdypy.studio.DraftStore, such as a GitHubDraftStore over game.crowdy_studio_github.

Performance

Python does no work per datagram. Receive, HMAC verification and decoding happen on CrowdyCPP's network thread, which never takes the GIL; Python sees one batch object per poll. Sends release the GIL, and a batch releases it once for the whole batch. An asyncio loop is woken through a socket, not by polling. Measured against CrowdyCPP on the same machine (benchmarks/README.md): a 200-entity batch costs 1.06x CrowdyCPP's own send path per entity, Python takes in two million verified notifications a second, a notification reaches an asyncio handler 47 µs after it hits the wire (p50), and a 60 Hz loop stays within 0.2 ms of its schedule while receiving 60,000 a second.

Development

uv sync                       # builds the extension (CMake, a C++20 compiler) and installs dev tools
uv run pytest tests/unit
uv run ruff check . && uv run ruff format --check . && uv run mypy

The live suites in tests/e2e/ run against a deployment when the CROWDY_E2E_* variables are set; docs/e2e-coverage.md lists them, how to configure them and the last live runs.

The gates CI runs, all from a clean checkout:

Gate Command
Vendored CrowdyCPP is the pinned commit's tree python scripts/vendor_crowdycpp.py --check
schema.gql and operations are CrowdyJS's at the pin python scripts/schema_sync.py --check
Generated code is current python scripts/codegen.py --check
The blocking client is generated from the async one python scripts/unasync.py --check
Parity with CrowdyJS python tools/parity/parity.py --crowdyjs ../CrowdyJS --check docs/parity-matrix.md
No internal names in the tree or the artifacts python scripts/ci/check_content_policy.py

AGENTS.md covers maintenance: re-pinning CrowdyJS and CrowdyCPP, the tier branches and the release path.

License

MIT. Wheels also contain CrowdyCPP (MIT), yyjson (MIT) and OpenSSL (Apache-2.0).

Metadata

Release files for crowdypy 0.34.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 crowdypy 0.34.0
File Size Uploaded Provenance Actions
crowdypy-0.34.0.tar.gz 1.6 MB With provenance Details for crowdypy-0.34.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for crowdypy 0.34.0
File Actions
crowdypy-0.34.0-cp314-cp314t-win_amd64.whl CPython 3.14 CPython 3.14 free-threading Windows x86-64 Details for crowdypy-0.34.0-cp314-cp314t-win_amd64.whl
crowdypy-0.34.0-cp314-cp314t-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64 Details for crowdypy-0.34.0-cp314-cp314t-musllinux_1_2_x86_64.whl
crowdypy-0.34.0-cp314-cp314t-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64 Details for crowdypy-0.34.0-cp314-cp314t-musllinux_1_2_aarch64.whl
crowdypy-0.34.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for crowdypy-0.34.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
crowdypy-0.34.0-cp314-cp314t-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.26+ ARM64, Linux glibc 2.28+ ARM64 Details for crowdypy-0.34.0-cp314-cp314t-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
crowdypy-0.34.0-cp314-cp314t-macosx_11_0_x86_64.whl CPython 3.14 CPython 3.14 free-threading macOS 11.0+ x86-64 Details for crowdypy-0.34.0-cp314-cp314t-macosx_11_0_x86_64.whl
crowdypy-0.34.0-cp314-cp314t-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 Details for crowdypy-0.34.0-cp314-cp314t-macosx_11_0_arm64.whl
crowdypy-0.34.0-cp312-abi3-win_amd64.whl CPython 3.12 abi3 Windows x86-64 Details for crowdypy-0.34.0-cp312-abi3-win_amd64.whl
crowdypy-0.34.0-cp312-abi3-musllinux_1_2_x86_64.whl CPython 3.12 abi3 Linux musl 1.2+ x86-64 Details for crowdypy-0.34.0-cp312-abi3-musllinux_1_2_x86_64.whl
crowdypy-0.34.0-cp312-abi3-musllinux_1_2_aarch64.whl CPython 3.12 abi3 Linux musl 1.2+ ARM64 Details for crowdypy-0.34.0-cp312-abi3-musllinux_1_2_aarch64.whl
crowdypy-0.34.0-cp312-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 abi3 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for crowdypy-0.34.0-cp312-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
crowdypy-0.34.0-cp312-abi3-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 abi3 Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for crowdypy-0.34.0-cp312-abi3-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
crowdypy-0.34.0-cp312-abi3-macosx_11_0_x86_64.whl CPython 3.12 abi3 macOS 11.0+ x86-64 Details for crowdypy-0.34.0-cp312-abi3-macosx_11_0_x86_64.whl
crowdypy-0.34.0-cp312-abi3-macosx_11_0_arm64.whl CPython 3.12 abi3 macOS 11.0+ ARM64 Details for crowdypy-0.34.0-cp312-abi3-macosx_11_0_arm64.whl

Total release size: 44.6 MB

Release files / crowdypy-0.34.0.tar.gz

Download URL crowdypy-0.34.0.tar.gz
Size 1.6 MB
Tags Source
SHA-256 checksum
How to use checksums
56dbb0fdb3791476ae6251e213707550f1ba3dd5ea8d1554ef11daab9ecef12c
BLAKE2b-256 checksum
How to use checksums
0093c483dc78d2106cf8bdb2f88c9a5e87bcdf932f17025711f2db341d965835
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp314-cp314t-win_amd64.whl

Download URL crowdypy-0.34.0-cp314-cp314t-win_amd64.whl
Size 2.8 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
0cca7fad01c6a383895688dfe96bbbf57df6befdf37cae1101d0a1431f90d630
BLAKE2b-256 checksum
How to use checksums
0565abc44463b3ca298716aeb8f45fa38e1e0f5a0cd2e195b02bec62adc156e2
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp314-cp314t-musllinux_1_2_x86_64.whl

Download URL crowdypy-0.34.0-cp314-cp314t-musllinux_1_2_x86_64.whl
Size 3.1 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
7816bc53a896fa81a48bfaa57995109b37d9715a557c16cad32d18fbf79c77a9
BLAKE2b-256 checksum
How to use checksums
54408da03412775a6b43b32b42efa225a9a026dbfbeac94d697ab3cb888a28fd
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp314-cp314t-musllinux_1_2_aarch64.whl

Download URL crowdypy-0.34.0-cp314-cp314t-musllinux_1_2_aarch64.whl
Size 3.5 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
b02ce85fb20d1f1e6b1532bc04fef269be2844409c75a1cda252683d03ab2bd9
BLAKE2b-256 checksum
How to use checksums
562a3170d5e908ed64c0862d6213508e5e1dee711d20c900a88b4d3d2c57edbf
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL crowdypy-0.34.0-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 3.0 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
1c4e5d627fccbfbc41712ad8b6c16b9d8bcbf19126d3ed3bda9c7cd297eef511
BLAKE2b-256 checksum
How to use checksums
0a5a20f578c94cdc4c79748ee1d04018bf86fa50cff1fe85f4d2f0050a0d4358
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp314-cp314t-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL crowdypy-0.34.0-cp314-cp314t-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 3.3 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
98bb263efa9cf61db544cd85601324431cdd628f806cfbcbe459d65a2bdddd00
BLAKE2b-256 checksum
How to use checksums
1f159b438568cf9468a485bc624ad795262273844e5ed83de28d0cd41ca8a601
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp314-cp314t-macosx_11_0_x86_64.whl

Download URL crowdypy-0.34.0-cp314-cp314t-macosx_11_0_x86_64.whl
Size 2.7 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
4a8cd9e4d153b52f881e96938896b8b664afcf1ae1c19d4e07eb7561401a14e6
BLAKE2b-256 checksum
How to use checksums
d939253b6108eee4377ddb82b0cdc3b034b296cad2df835cd059431ec115f983
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp314-cp314t-macosx_11_0_arm64.whl

Download URL crowdypy-0.34.0-cp314-cp314t-macosx_11_0_arm64.whl
Size 3.0 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
59e891ae68cd050420e1e3fae8b7362d69cc44eeee717ca4a2d1fa040107f290
BLAKE2b-256 checksum
How to use checksums
a4f40e4f1f623f82bb3e23bc560d4b2650d7a6ed9da03a9c54ff1fb58484b555
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp312-abi3-win_amd64.whl

Download URL crowdypy-0.34.0-cp312-abi3-win_amd64.whl
Size 2.7 MB
Tags CPython 3.12 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
f77ed89cfb9019b00bfa2c85679529657165762de94d82bb8268f70abe2f462e
BLAKE2b-256 checksum
How to use checksums
5fb9fe65f46047914248876ea34af9155f537ca63818f422e21dae19de88b2d9
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp312-abi3-musllinux_1_2_x86_64.whl

Download URL crowdypy-0.34.0-cp312-abi3-musllinux_1_2_x86_64.whl
Size 3.1 MB
Tags CPython 3.12 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
3f62df6fd632706c1cb08ba21e810b601a8523555b4db61d1a564d674472f1ca
BLAKE2b-256 checksum
How to use checksums
7aa7987cae3c85278d89301a1265ab31d1eee22adf68a2e727ed8d2c4a296aa6
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp312-abi3-musllinux_1_2_aarch64.whl

Download URL crowdypy-0.34.0-cp312-abi3-musllinux_1_2_aarch64.whl
Size 3.4 MB
Tags CPython 3.12 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
44d61943baa5f37a7607df3682acfe6e66296bc43a49fb06ed4cefc1780218a5
BLAKE2b-256 checksum
How to use checksums
0a6e045243f82315451ab51af98fb7dd2b77c9ffbee843e737afb2314902215d
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp312-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL crowdypy-0.34.0-cp312-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 3.0 MB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
fa9537d2d5988ba68f096028bc36271e8087145a98004da5f0c85dc4c5dc31c6
BLAKE2b-256 checksum
How to use checksums
c298855821e62a68942970070961ea4bfd53a8ae99abbde86647726651b66c66
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp312-abi3-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL crowdypy-0.34.0-cp312-abi3-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 3.3 MB
Tags CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
58b3b68131f13e859e58576e2529980f6cef42fdef60a49614d5310d5459f92e
BLAKE2b-256 checksum
How to use checksums
9cf8068d4097dbeb526ab44fdb4cdb80c35cb5d95ebf881903220a119735291f
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp312-abi3-macosx_11_0_x86_64.whl

Download URL crowdypy-0.34.0-cp312-abi3-macosx_11_0_x86_64.whl
Size 2.7 MB
Tags CPython 3.12 abi3 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
cdca90ccea426676f5652f922be276811597fbb40c46598b0946367eb5af2af8
BLAKE2b-256 checksum
How to use checksums
c135c3319a83d9741fd2aebc7b523b75821471643343a6252a3a143281482ac5
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 18, 2026.

Transparency log

Release files / crowdypy-0.34.0-cp312-abi3-macosx_11_0_arm64.whl

Download URL crowdypy-0.34.0-cp312-abi3-macosx_11_0_arm64.whl
Size 3.0 MB
Tags CPython 3.12 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
4c7a5253c2f65c2b56f7e7eed2b553952257725f66db7ee25decd0f51056f0dd
BLAKE2b-256 checksum
How to use checksums
9d8f524aac2f5a570c997e2904f55c29ee5ccbc0878fd6f4b894e391c9ae3275
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 18, 2026.

Transparency log

Security for crowdypy 0.34.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 15 files in this release have been uploaded with provenance metadata.

Select from 15 files

Attestation for crowdypy-0.34.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 18, 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

0.34.0 This release

15 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