Skip to main content

rcswx

RCSWX reimplements the Recursive Constrained Smith–Waterman crossover algorithm for grammar-based neural architecture search proposed in Evolutionary Architecture Search through Grammar-Based Sequence Alignment (see the original implementation). Its portable Rust-backed API aligns and applies edits to architecture data, with optional PyTorch integration.

Installation

RCSWX supports Python 3.12–3.14. Its minimal package has the native Python binding and portable architecture API only: it does not install or import Torch, NumPy, or SciPy.

uv add rcswx                         # Portable alignment/application only.
uv add 'rcswx[torch]'                # PyTorch grammar, capture, and module APIs.
uv add 'rcswx[reference]'            # NumPy/SciPy reference sampler only.
uv add 'rcswx[torch,reference]'      # Both optional surfaces.

Equivalent uv pip install or python -m pip install commands work in an active virtual environment. Source builds require Rust/Cargo.

For source development, first enter the locked Nix shell on NixOS, then install both optional surfaces deliberately:

nix develop
make sync
make develop

make sync, make develop, and make test pass --all-extras; a plain minimal wheel install remains a separately tested contract.

Portable API and sampling

Inputs are data-only grammar occurrence trees, not arbitrary TensorFlow, Keras, or PyTorch models. A structural application does not need a scientific Python stack:

from rcswx import Architecture, apply_edits, edit_path

first = Architecture.from_tree(("sequential", ("relu",)))
second = Architecture.from_tree(("sequential", ("sigmoid",)))
explicit_plan = edit_path(first, second)

unchanged = apply_edits(explicit_plan, explicit_plan.select([]))
seeded_plan = edit_path(first, second)
seeded_child = apply_edits(seeded_plan, seeded_plan.sample(seed=42))

Architecture.from_dict/from_json validate schema version 1; to_dict and to_json expose its wire representation. Child edges are occurrence indices. Logical node IDs are canonical decimal strings, may repeat, and have no fixed integer width. Parameters, provenance, and input assumptions remain opaque JSON; the core preserves their numbers and keys rather than interpreting private metadata markers.

An explicit empty selection starts from parent two. Selections belong to one plan; they cannot be applied to another plan. Legacy trees retain historical second-parent ID updates, and structural changes to those trees invalidate subsequent selection or application. Portable architectures are immutable.

edit_path(..., limits={...}) accepts max_work, max_output, and max_allocation_bytes quotas. The last bounds accounted native allocations, not process RSS. profile=True enables diagnostic stage timings; leave it disabled for primary performance measurements.

Native wavefront execution is opt-in at build time and per call:

make develop-parallel  # Or: make wheel-parallel; install that exact wheel.
make parallel-check parallel-test

Then use edit_path(first, second, workers=2) (or Alignment(..., workers=2)). The default workers=1 is serial and never initializes the pool. workers=-1 uses the private pool's capacity; other positive integers bound this call's simultaneous compute jobs, capped at that capacity. Concurrent calls share the same bounded pool. Boolean/non-integer counts, zero, and values below -1 are rejected before legacy parent preparation. Serial-only builds reject parallel requests; WebAssembly stays serial even with the Cargo feature enabled.

plan.execution reports capability, requested/resolved workers, pool capacity, parallel/serial cells, job overlap, scratch reservation and fallback counts. Algorithm statistics and ordered plans are unchanged. Uneconomic, aliased, or scratch-limited waves can run serially. The coordinator handles callbacks and signals; interrupted calls join their jobs before raising. Serial callback re-entry is supported; parallel callback re-entry and reuse of an initialized pool after fork fail promptly. Use serial execution or a fresh interpreter in a forked child. Parallel execution helps sufficiently history-heavy waves, not every wide matrix; retain the serial default for unmeasured workloads. See wavefront design and measurements for the execution contract, performance evidence, and limits.

On legacy/PyTorch trees, the Limiter's memory_crossover RSS guard remains host-side. Retained native operations poll it at their first checkpoint, every 1,024 checkpoints thereafter, and before returning a successful native result. Work/output/allocation quotas still account every checkpoint in Rust; they are not throttled with host polling. RSS checks are sampled and can overshoot a threshold between polls, so they are not a hard process-memory ceiling. Parallel calls additionally poll elapsed time at 10 ms intervals while waiting for compute jobs. This does not change canonical work or allocation counters.

Native ChaCha12 sampling is the default. It is seeded through RCSWX and does not consume NumPy's global RNG; a structural seed never seeds PyTorch weight initialization. Select the historical numerical route explicitly with sampler="reference" after installing rcswx[reference].

Native seeds are integers in [0, 2**256) or exactly 32 bytes; integer seeds use little-endian encoding. A stream can be shared across calls and checkpointed without importing NumPy:

from rcswx import NativeRng

stream = NativeRng(42)
checkpoint = stream.state()
selection = seeded_plan.sample(rng=stream)
replay = NativeRng.from_state(checkpoint)
assert seeded_plan.sample(rng=replay).indices == selection.indices

The versioned replay state names the generator and its position. Reference mode uses NumPy's global RNG instead: seed NumPy explicitly and do not pass native seed/rng arguments with sampler="reference". The two samplers share the discrete probability law, not seed-to-child identity.

Tree-level crossover and module-level crossover are separate APIs. A module crossover creates a fresh child without transferring learned weights, buffer values, or optimizer state; provenance capture is supported, but arbitrary unannotated-model import is not. The structural core is portable, while TensorFlow/Keras integration and a browser UI are not delivered here.

See examples/ for the portable example, PyTorch construction, explicit edit selection, tree crossover, capture/build, and converter examples.

Reference compatibility

RCSWX is a corrected port, not a bug-for-bug replica of the original einsearch implementation. The independent oracle is pinned to commit 3f44ddf086bee0c213404e240ee0adf99e3e1501 and hash-checked by tests/reference/original.py.

The following corrections deliberately differ from that source:

  • Recursive edits and wrapper boundaries use physical source occurrences rather than remapped trace coordinates. Swap bookkeeping distinguishes wrappers even when their logical IDs repeat.
  • Adding a binary wrapper requires added material only in a branch that would otherwise be empty. The original can also require an addition in the retained branch, including an impossible empty enabler group.
  • Zero-cost matches do not replace unchanged modules, routing functions, or wrapper payloads. When an accompanying binary-wrapper match requires a branch reorientation, application relinks its children and rebinds its anchor ID without copying the matched subtree from parent one.

These corrections can change edit application order, valid selections, offspring, and failure behavior. sampler="reference" selects the historical NumPy/SciPy numerical route on the current edit plan; it does not restore the original operator's bugs or guarantee historical seed-to-child identity.

Reference tests retain exact comparisons for unchanged behavior. The known branch-constraint correction is explicit in the oracle comparison; separate regressions check wrapper boundaries, ordered topology, and payload ownership. Passing those checks is not a claim of universal original-output parity or tensor-level validity for every generated architecture.

PyTorch capture and persistence

rcswx.torch.build(architecture, input_spec=...) creates a fresh model and attaches data-only structural provenance. capture(model) recovers it and rejects stale topology, shared modules, shared parameter/buffer objects, and distinct tensors sharing backing storage. External modules need an explicitly registered converter; unsupported structures are not approximated.

For retained RCSWX models, build(capture(model)) preserves captured per-module train/eval modes and per-tensor dtype, device, and gradient requirements; it initializes fresh parameters and buffers. Explicit BuildOptions override device, floating/complex dtype, or training mode. rcswx.torch.crossover and crossover_with_report capture both parents, call the portable engine, and build a fresh child without retries or a hidden validation forward pass. Their default is compatible parent materialization and parent one's root training mode; ambiguous dtype/device layouts require an explicit build option.

Use rcswx.torch.save/load for a managed checkpoint containing a validated manifest and state dictionary. Loading rebuilds only supported registered grammar/converter structures and uses Torch's weights-only loader. Capture describes architecture, not optimizer state or an arbitrary executable model.

Wheel and WebAssembly portability gates

Build one exact wheel, then test that exact artifact in fresh minimal, Torch, reference, and combined environments. The gate checks metadata, missing-extra errors, root import isolation, and runnable examples; it never accepts an editable import as proof.

make wheel
RCSWX_WHEEL=dist/rcswx-0.5.2-...whl RCSWX_PYTHON=python3.12 make wheel-test

For a parallel-capable artifact, use make wheel-parallel, then RCSWX_WHEEL=dist/parallel/rcswx-0.5.2-...whl make wheel-parallel-test. That gate verifies capability and serial/parallel plan parity in every surface. make wasm-parallel-check executes the core and frozen oracle in Node with the feature enabled, proving that native threads do not enter the WASM dependency graph.

The Rust workspace also builds a reusable browser package and an interactive worker-owned example. It runs the existing core, with deterministic slider prefixes, seeded sampling, and bounded recordings of actual recursive alignment:

nix develop
make web-demo  # open the displayed /rcswx/ URL
make web-test  # exact package in Chromium, Firefox, and WebKit

See WASM consumer contracts and the standalone example. The original development-only core gate remains separate: make wasm-check compiles the core—not PyO3—for wasm32-unknown-unknown, and make wasm-smoke executes its decode/analyze/full-history/apply, probability, seeded draw and raw RNG-vector smoke in Node.

The workspace declares Rust 1.85 as its MSRV. The Nix shell pins Rust 1.85.0 with the WASM target and supplies the local wasm-bindgen-test-runner and Node; it does not install a global target or runner. The portable core's target libraries are serialization (serde/serde_json), arbitrary IDs (num-bigint), libm, and rand_chacha/rand_core. Their installed Cargo manifests declare MIT for libm and MIT OR Apache-2.0 for the other listed libraries. The dev-only execution harness pins wasm-bindgen-test 0.3.77, whose wasm-bindgen 0.2.127 matches the locked Nix CLI; its manifest declares MIT OR Apache-2.0. Native parallel builds additionally link Rayon and its MIT OR Apache-2.0 dependencies. Wheels retain the original algorithm attribution and the verbatim numerical and optional parallel dependency notices in LICENSE.rust-dependencies.

Cite

@inproceedings{gomez2026evolutionary,
  author    = {Gómez Martín, Adri and Möller, Felix and McDonagh, Steven and
               Abella, Monica and Desco, Manuel and Crowley, Elliot J. and
               Klein, Aaron and Ericsson, Linus},
  title     = {Evolutionary Architecture Search through Grammar-Based Sequence Alignment},
  booktitle = {International Conference on Automated Machine Learning (AutoML)},
  year      = {2026},
  url       = {https://arxiv.org/abs/2512.04992}
}

License

MIT

Metadata

Release files for rcswx 0.5.2

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

Source distribution (sdist)

Source distribution for rcswx 0.5.2
File Size Uploaded Provenance Actions
rcswx-0.5.2.tar.gz 191.7 kB With provenance Details for rcswx-0.5.2.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for rcswx 0.5.2
File Actions
rcswx-0.5.2-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for rcswx-0.5.2-cp314-cp314-win_amd64.whl
rcswx-0.5.2-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details for rcswx-0.5.2-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
rcswx-0.5.2-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64 Details for rcswx-0.5.2-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
rcswx-0.5.2-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for rcswx-0.5.2-cp314-cp314-macosx_11_0_arm64.whl
rcswx-0.5.2-cp314-cp314-macosx_10_12_x86_64.whl CPython 3.14 CPython 3.14 macOS 10.12+ x86-64 Details for rcswx-0.5.2-cp314-cp314-macosx_10_12_x86_64.whl
rcswx-0.5.2-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for rcswx-0.5.2-cp313-cp313-win_amd64.whl
rcswx-0.5.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details for rcswx-0.5.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
rcswx-0.5.2-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ ARM64 Details for rcswx-0.5.2-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
rcswx-0.5.2-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for rcswx-0.5.2-cp313-cp313-macosx_11_0_arm64.whl
rcswx-0.5.2-cp313-cp313-macosx_10_12_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.12+ x86-64 Details for rcswx-0.5.2-cp313-cp313-macosx_10_12_x86_64.whl
rcswx-0.5.2-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for rcswx-0.5.2-cp312-cp312-win_amd64.whl
rcswx-0.5.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details for rcswx-0.5.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
rcswx-0.5.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64 Details for rcswx-0.5.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
rcswx-0.5.2-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for rcswx-0.5.2-cp312-cp312-macosx_11_0_arm64.whl
rcswx-0.5.2-cp312-cp312-macosx_10_12_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.12+ x86-64 Details for rcswx-0.5.2-cp312-cp312-macosx_10_12_x86_64.whl

Total release size: 10.4 MB

Release files / rcswx-0.5.2.tar.gz

Download URL rcswx-0.5.2.tar.gz
Size 191.7 kB
Tags Source
SHA-256 checksum
How to use checksums
0a8690cfb11946751040f5a38cf199c57ba5a3d435a97883e75b0fc3855515d6
BLAKE2b-256 checksum
How to use checksums
a9be1fc9bc5722962aa294bd7431728b13b05ad2a58d705d538d2d0f009e835a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp314-cp314-win_amd64.whl

Download URL rcswx-0.5.2-cp314-cp314-win_amd64.whl
Size 567.9 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
65bc1a8fba409eba7753b126b251e0b5775e211a93049be620f9a06ec1d2a5da
BLAKE2b-256 checksum
How to use checksums
b83e828345aebbb1d20f816a3a25a7cbc1331e194a3ba6dc47928e6707642aa9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL rcswx-0.5.2-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 743.4 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
469c58d502a94193474afd7d1a36b3b22c7c19dee3621e1f2f22b4327ef62fb4
BLAKE2b-256 checksum
How to use checksums
becfd5ee9d6eb888ac4b7d3d0745bb5711bae366eaefb1b5b6b12e2f0b513553
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL rcswx-0.5.2-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 716.5 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
fada814bcf41493bd49ffb9494469a1402e6b574c430c251adbe5f85da844ba0
BLAKE2b-256 checksum
How to use checksums
19df716d0350f897049c9a9ea78f03013b4cdb98decc18a07d0e0ae75a472fd2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp314-cp314-macosx_11_0_arm64.whl

Download URL rcswx-0.5.2-cp314-cp314-macosx_11_0_arm64.whl
Size 674.2 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
9b4446091413a82830c882ad5e96431ab77f08c08f34ed6afc50034618231ed0
BLAKE2b-256 checksum
How to use checksums
60669109fd9bcef6092461e71ca85b2a317dbde091e1a5cd714ae180df8051de
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp314-cp314-macosx_10_12_x86_64.whl

Download URL rcswx-0.5.2-cp314-cp314-macosx_10_12_x86_64.whl
Size 697.2 kB
Tags CPython 3.14 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
8d9c2cbe194094f4bc72c5948ff3f286bd0f384cd6e1a04a1b19c40b9cfe0ad4
BLAKE2b-256 checksum
How to use checksums
8a9f3ef4a44f7de3899d575d789401647c4f8852fa9a40a411615245735b010b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp313-cp313-win_amd64.whl

Download URL rcswx-0.5.2-cp313-cp313-win_amd64.whl
Size 567.4 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
d34eae01cf829263a837d08c347304cdf132adc96afef98f5f76f66252e284ab
BLAKE2b-256 checksum
How to use checksums
85754a65c468dd908654ec12af5d5e8fa435c5ce40a4129cd943afb3c14f9a50
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL rcswx-0.5.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 744.1 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
1cb6dd59994bb418d5597766d4e3dd5824c7d2dc24e070b878f0485ee38625e1
BLAKE2b-256 checksum
How to use checksums
02e87bea57a33e600b19e52f15ec1bb5338bfc6fb49b1674282a6e906d0e6c99
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL rcswx-0.5.2-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 717.5 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
db45bf318118ee8315255531da5d2e990a5a59d8e98583bc55aff8e2f2c4ffac
BLAKE2b-256 checksum
How to use checksums
bd6bb35c9e83f7e7b88befb7b07566f32c90a715d5da47aecbb17293368b0786
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp313-cp313-macosx_11_0_arm64.whl

Download URL rcswx-0.5.2-cp313-cp313-macosx_11_0_arm64.whl
Size 674.8 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
38d4357b242e6e0898926e89bd68433bdf21f63fa47a685403b4f65cd1301c3c
BLAKE2b-256 checksum
How to use checksums
d123e30aa8fcea20fabae72bf65201c71c4440301896c792fb5f227a40b7211b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp313-cp313-macosx_10_12_x86_64.whl

Download URL rcswx-0.5.2-cp313-cp313-macosx_10_12_x86_64.whl
Size 698.3 kB
Tags CPython 3.13 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
36e9ab3daa79bc7d2d170424447a9d6a8dd6c1cab5347ae18a5ad37953ab708e
BLAKE2b-256 checksum
How to use checksums
d326e358080e25890dad91eff3787f2becc21824b501250e80b53f8813022445
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp312-cp312-win_amd64.whl

Download URL rcswx-0.5.2-cp312-cp312-win_amd64.whl
Size 567.7 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
d88e785f4a50d59d7e385fc3bcdc9d1fad8a4d0fc57dc6bb18925514249eef0d
BLAKE2b-256 checksum
How to use checksums
b9da2bd0cee14845dca2be664b11b9bc6800f7a1a705144cfcbf179824bb86ed
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL rcswx-0.5.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 744.9 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
54f149e74d4d738d499261c0e17d0fe8e9000985efc1501a3e16d1d710ccaca2
BLAKE2b-256 checksum
How to use checksums
74d93b94eb2f86a542fd37bb20e3fc948d41ca02819d68b0bddda566b2bce882
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL rcswx-0.5.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 718.6 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
523302cc2089109b1697ef6ac41c5b54049e3655bdd0df78cf258c5e19cc27e5
BLAKE2b-256 checksum
How to use checksums
1532a92bb35a1f3b3f440c94ba6c1f97c91506fb97b56efe05e2c451c10ba5f5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp312-cp312-macosx_11_0_arm64.whl

Download URL rcswx-0.5.2-cp312-cp312-macosx_11_0_arm64.whl
Size 675.4 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
77fcf8280832ba757f3e0b6be521644bec7d0ee581aeeb13d8a23222c483fbcc
BLAKE2b-256 checksum
How to use checksums
204d74917ebeaf075af55d737b6ae3d92fd6047d7ed4c293b017f6432ae7aae5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / rcswx-0.5.2-cp312-cp312-macosx_10_12_x86_64.whl

Download URL rcswx-0.5.2-cp312-cp312-macosx_10_12_x86_64.whl
Size 698.8 kB
Tags CPython 3.12 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
ade499a9d0bd0d6075734c6aefdb87b675e317f8606d14fc4335aef11ff9f3b0
BLAKE2b-256 checksum
How to use checksums
8c9e3bfec7d588c1a8c600677a56fa3b7dff144d891a68f18ef775fa0936c077
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Security for rcswx 0.5.2

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 16 files in this release have been uploaded with provenance metadata.

Select from 16 files

Attestation for rcswx-0.5.2.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 Sep 26, 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.

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