Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Monarch 🦋

Monarch is a distributed programming framework for PyTorch based on scalable actor messaging. It provides:

  1. Remote actors with scalable messaging: Actors are grouped into collections called meshes and messages can be broadcast to all members.
  2. Fault tolerance through supervision trees: Actors and processes form a tree and failures propagate up the tree, providing good default error behavior and enabling fine-grained fault recovery.
  3. Point-to-point RDMA transfers: cheap registration of any GPU or CPU memory in a process, with the one-sided transfers based on libibverbs
  4. Distributed tensors: actors can work with tensor objects sharded across processes

Monarch code imperatively describes how to create processes and actors using a simple python API:

from monarch.actor import Actor, endpoint, this_host

# spawn 8 trainer processes one for each gpu
training_procs = this_host().spawn_procs({"gpus": 8})


# define the actor to run on each process
class Trainer(Actor):
    @endpoint
    def train(self, step: int): ...


# create the trainers
trainers = training_procs.spawn("trainers", Trainer)

# tell all the trainers to take a step
fut = trainers.train.call(step=0)

# wait for all trainers to complete
fut.get()

The introduction to monarch concepts provides an introduction to using these features.

📖 Documentation

View Monarch's hosted documentation at this link.

Installation

Installing from Pre-built Wheels

Monarch provides pre-built wheels that work regardless of what version of PyTorch you have installed. You can get these with pip or uv: For the pinned nightly examples, replace YYYYMMDD with the build date.

  • Using PIP:
    • stable: pip install torchmonarch
    • nightly: pip install --pre torchmonarch
    • specific: pip install torchmonarch==0.9.0.devYYYYMMDD
  • Using UV - note, you can also just use uv pip install ... and match the above pip commands; but the ones below add monarch to your UV project properly.
    • stable: uv add torchmonarch
    • nightly: uv add --prerelease=allow torchmonarch
    • specific: uv add torchmonarch==0.9.0.devYYYYMMDD

Build and Install from Source

Note: Building from source requires additional system dependencies. These are needed at build time only, not at runtime.

Monarch uses uv for fast, reliable Python package management. If you don't have uv installed:

# Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
# Or on macOS
brew install uv

Configuring PyTorch Index: By default, Monarch builds with PyTorch from the pytorch-cu132 index (CUDA 13.2). To use a different CUDA version:

  • Edit [tool.uv.sources] in pyproject.toml to point to a different index (e.g., pytorch-cu130, or pytorch-cpu)
  • Or use --extra-index-url when running uv:
    uv sync --extra-index-url https://download.pytorch.org/whl/cu130
    

Understanding Tensor Engine

Monarch includes distributed tensor and RDMA APIs. The tensor engine builds on any platform, including CPU-only hosts and macOS; GPU-specific pieces (NCCL, RDMA, rdmaxcel) layer on top and only build on Linux with a CUDA or ROCm toolchain installed. If you want a lighter-weight version of Monarch (actors only, no torch dependency), set USE_TENSOR_ENGINE=0.

By default, Monarch builds with tensor_engine enabled. To build without it:

USE_TENSOR_ENGINE=0 uv sync

Note: Building without tensor_engine means you won't have access to the distributed tensor or RDMA APIs. Torch is required to use tensor_engine, and the latest stable torch is ABI compatible with the latest versioned torchmonarch

Selecting a GPU platform: The MONARCH_GPU_PLATFORM environment variable controls which GPU libraries the build links against. It accepts:

  • cuda — build against CUDA (NCCL + RDMA).
  • rocm — build against ROCm.
  • none — force a CPU-only tensor engine even on a host where CUDA or ROCm is installed.

Leaving it unset auto-detects whichever toolchain is present. Setting it explicitly is required when both CUDA and ROCm are installed, and none is the explicit opt-out when you want the CPU tensor engine on a GPU-capable host.

# Force a CPU-only tensor engine (no CUDA/ROCm/RDMA libraries required)
MONARCH_GPU_PLATFORM=none uv sync

# Force CUDA on a host that also has ROCm
MONARCH_GPU_PLATFORM=cuda uv sync

Build Dependencies by Platform

On Fedora distributions
# Install nightly rust toolchain
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
rustup toolchain install nightly
rustup default nightly

# Install non-python dependencies
sudo dnf install -y cmake ninja-build protobuf-compiler libunwind

# Install the correct cuda and cuda-toolkit versions for your machine
sudo dnf install cuda-toolkit-13-2 cuda-13-2

# Install clang-devel, nccl-devel, and libstdc++-static
sudo dnf install clang-devel libnccl-devel libstdc++-static

# Install RDMA libraries (needed for tensor_engine builds)
sudo dnf install -y libibverbs rdma-core libmlx5 libibverbs-devel rdma-core-devel

# Clone and sync dependencies
git clone https://github.com/meta-pytorch/monarch.git
cd monarch

# Install in development mode with all dependencies
uv sync

# Or install without tensor_engine
USE_TENSOR_ENGINE=0 uv sync

# Verify installation
uv run python -c "from monarch import actor; print('Monarch installed successfully')"

# Rebuild (e.g., after changing Rust code)
USE_TENSOR_ENGINE=0 uv pip install -e .
On Ubuntu distributions
# Install nightly rust toolchain
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
source $HOME/.cargo/env
rustup toolchain install nightly
rustup default nightly

# Install Ubuntu-specific system dependencies
sudo apt install -y cmake ninja-build protobuf-compiler libunwind-dev clang

# Set clang as the default C/C++ compiler
export CC=clang
export CXX=clang++

# Install the correct cuda and cuda-toolkit versions for your machine
sudo apt install -y cuda-toolkit-13-2 cuda-13-2

# Install RDMA libraries (needed for tensor_engine builds)
sudo apt install -y rdma-core libibverbs1 libmlx5-1 libibverbs-dev

# Clone and sync dependencies
git clone https://github.com/meta-pytorch/monarch.git
cd monarch

# Install in development mode with all dependencies
uv sync

# Or install without tensor_engine (CPU-only)
USE_TENSOR_ENGINE=0 uv sync

# Verify installation
uv run python -c "from monarch import actor; print('Monarch installed successfully')"

# Rebuild (e.g., after changing Rust code)
USE_TENSOR_ENGINE=0 uv pip install -e .
On non-CUDA machines

You can also build Monarch on non-CUDA machines (e.g., macOS laptops) for CPU-only usage. The tensor engine itself works on CPU; only the GPU-specific bits (NCCL, RDMA, rdmaxcel) are skipped. Auto-detection handles hosts with no CUDA or ROCm installed. If your host does have a GPU toolchain installed but you want the CPU tensor engine anyway, set MONARCH_GPU_PLATFORM=none.

# Install nightly rust toolchain
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
rustup toolchain install nightly
rustup default nightly

# Clone and sync dependencies
git clone https://github.com/meta-pytorch/monarch.git
cd monarch

# Build the CPU tensor engine (auto-detects no GPU)
uv sync

# Or, to skip the tensor engine entirely (actors only, no torch required)
USE_TENSOR_ENGINE=0 uv sync

# Verify installation
uv run python -c "from monarch import actor; print('Monarch installed successfully')"

Alternative: Using pip

If you prefer to use pip instead of uv:

# After installing system dependencies (see above)

# Install build dependencies

# Build and install Monarch
pip install .

# Or for development
pip install -e .

# Without tensor_engine
USE_TENSOR_ENGINE=0 pip install -e .

Building a Docker Image from Source

To build a Docker image that bundles your from-source build of Monarch — for example, to run Monarch on a Kubernetes cluster — first build a wheel, then build the image from that wheel. This picks up changes to both the Rust and Python code.

# Make sure to build for python 3.12 since the pytorch base image uses that python version
uv python pin 3.12
# Build the binary distribution, outputs to "dist/" directory.
# --no-build-isolation allows using cached rust builds which speeds up subsequent
# iterations.
uv build --no-build-isolation --wheel

# With docker:
# Build and tag a docker image with your build of monarch. You can update the
# PYTORCH_TAG to use a different base image depending on your needs.
# The nightly dockerfile is used because it uses the package you already built,
# rather than downloading from PyPI. The wheels are supplied through the
# "monarch-wheels" named build context, which the Dockerfile copies from.
docker build -f Dockerfile.nightly \
  -t $USER/monarch:local-tag \
  --build-arg PYTORCH_TAG=2.16.0.dev20261102-cuda13.2-cudnn9-runtime \
  --build-context monarch-wheels=dist \
  .

# Push so it's available to the kubernetes cluster.
# Either (a) push to a container registry so your cluster can access it.
# Might be slow based on your upload speed and the size of the container.
docker push $USER/monarch:latest
# Or (b) if you have a fully local kubernetes cluster you can change it to
# imagePullPolicy: Never in the manifest and it'll use the image locally. This
# is the fastest iteration speed.

# With podman + kind:
# Same build command, replace "docker" with "podman"
# Save image to archive
podman save localhost/$USER/monarch:local-tag -o /tmp/monarch-image
# Then push to your kind cluster for local dev:
KIND_EXPERIMENTAL_PROVIDER=podman kind load image-archive /tmp/monarch-image -n monarch-cluster

Then point your deployment at the new image. Make sure to prepend the registry you used for docker login, like ghcr.io or docker.io, and that you have pushed the image first.

Running examples

Check out the examples/ directory for demonstrations of how to use Monarch's APIs.

We'll be adding more examples as we stabilize and polish functionality!

Running tests

We have both Rust and Python unit tests. Rust tests are run with cargo-nextest and Python tests are run with pytest.

Rust tests

Important: Monarch's Rust code uses PyO3 to interface with Python, which means the Rust binaries need to link against Python libraries. Before running Rust tests, you need to have a Python environment activated (conda, venv, or uv):

# If using uv (recommended)
uv sync  # This creates and activates a virtual environment
uv run cargo nextest run  # Run tests within the uv environment

# Or if using conda
conda activate monarchenv
cargo nextest run

# Or if using venv
source .venv/bin/activate
cargo nextest run

Without an active Python environment, you'll get Python linking errors like:

error: could not find native static library `python3.12`, perhaps an -L flag is missing?

Installing cargo-nextest:

# We use cargo-nextest to run our tests, as they provide strong process isolation
# between every test.
# Here we install it from source, but you can instead use a pre-built binary described
# here: https://nexte.st/docs/installation/pre-built-binaries/
cargo install cargo-nextest --locked

cargo-nextest supports all of the filtering flags of "cargo test".

Python tests

# Install test dependencies (if not already installed via uv sync)
uv sync --group test

# Run unit tests with uv
uv run pytest python/tests/ -v -m "not oss_skip"

# Or if using pip
pip install --group test -e .
pytest python/tests/ -v -m "not oss_skip"

Disabling flaky CI tests

If a test is consistently failing in OSS CI and needs to be temporarily disabled without a code change, open a GitHub issue on this repo with a title of the form:

DISABLED <test-name>

At the start of each CI run, scripts/fetch_disabled_tests.py fetches all open issues whose titles start with DISABLED and skips the named tests. Closing the issue re-enables the test on the next run.

Naming format:

  • Rust (cargo nextest): use the test name exactly as it appears in nextest output: <binary> <module::path::test_fn>, e.g. DISABLED hyperactor proc::tests::test_child_lifecycle
  • Python (pytest): use a test function name, full node ID, or structural node-ID prefix. For example, DISABLED test_my_function skips that function (including all parameterizations), while DISABLED python/tests/test_example.py skips the entire file.

Overriding skips locally

To run a test that is currently disabled via a GitHub issue, you can override the fetched skip lists by creating the files before running scripts/fetch_disabled_tests.py. The script will not overwrite files that already exist:

  • disabled_tests.txt — controls which Python tests are skipped. Create this file with only the tests you want to skip (or leave it empty to skip none).
  • .config/nextest-filter.txt — controls which Rust tests are skipped. Write a nextest filter expression here (e.g. all() to run all tests, or not (test(some_test)) to skip only specific ones).

For example, to run all tests locally regardless of open issues:

echo -n "" > disabled_tests.txt
echo "all()" > .config/nextest-filter.txt
uv run python scripts/fetch_disabled_tests.py   # will skip both writes
uv run pytest python/tests/ -v -m "not oss_skip"

Citation

If you use Monarch in your research, please cite it as:

@software{monarch2025,
  title = {Monarch: A distributed programming framework for PyTorch},
  author = {{Monarch maintainers and contributors}},
  url = {https://github.com/meta-pytorch/monarch},
  license = {BSD-3-Clause},
  year = {2025}
}

License

Monarch is BSD-3 licensed, as found in the LICENSE file.

Third Party Notice

RDMA Core

When built with RDMA support, Monarch statically links these libraries from rdma-core: libibverbs, libmlx5, libefa and librdma_util. Monarch's source file rdmaxcel-sys/src/mlx5_ifc_subset.h is also derived from rdma-core.

Most rdma-core files are offered under a choice of GPL-2.0 or a BSD license. Monarch uses them under the BSD license. Copies of applicable licenses can be found at:

For file-by-file copyright attribution and licensing, refer to the rdma-core repository linked above.

Metadata

Release files for torchmonarch 0.9.0.dev20261120

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

Built distributions (wheels)

Table of built distributions (wheels) for torchmonarch 0.9.0.dev20261120
File Actions
torchmonarch-0.9.0.dev20261120-cp314-cp314t-manylinux2014_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Details for torchmonarch-0.9.0.dev20261120-cp314-cp314t-manylinux2014_x86_64.whl
torchmonarch-0.9.0.dev20261120-cp314-cp314t-manylinux2014_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64 Details for torchmonarch-0.9.0.dev20261120-cp314-cp314t-manylinux2014_aarch64.whl
torchmonarch-0.9.0.dev20261120-cp314-cp314t-macosx_11_0_universal2.whl CPython 3.14 CPython 3.14 free-threading macOS 11.0+ universal2 (ARM64, x86-64) Details for torchmonarch-0.9.0.dev20261120-cp314-cp314t-macosx_11_0_universal2.whl
torchmonarch-0.9.0.dev20261120-cp314-cp314-manylinux2014_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.9.0.dev20261120-cp314-cp314-manylinux2014_x86_64.whl
torchmonarch-0.9.0.dev20261120-cp314-cp314-manylinux2014_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.9.0.dev20261120-cp314-cp314-manylinux2014_aarch64.whl
torchmonarch-0.9.0.dev20261120-cp314-cp314-macosx_11_0_universal2.whl CPython 3.14 CPython 3.14 macOS 11.0+ universal2 (ARM64, x86-64) Details for torchmonarch-0.9.0.dev20261120-cp314-cp314-macosx_11_0_universal2.whl
torchmonarch-0.9.0.dev20261120-cp313-cp313-manylinux2014_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.9.0.dev20261120-cp313-cp313-manylinux2014_x86_64.whl
torchmonarch-0.9.0.dev20261120-cp313-cp313-manylinux2014_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.9.0.dev20261120-cp313-cp313-manylinux2014_aarch64.whl
torchmonarch-0.9.0.dev20261120-cp313-cp313-macosx_11_0_universal2.whl CPython 3.13 CPython 3.13 macOS 11.0+ universal2 (ARM64, x86-64) Details for torchmonarch-0.9.0.dev20261120-cp313-cp313-macosx_11_0_universal2.whl
torchmonarch-0.9.0.dev20261120-cp312-cp312-manylinux2014_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.9.0.dev20261120-cp312-cp312-manylinux2014_x86_64.whl
torchmonarch-0.9.0.dev20261120-cp312-cp312-manylinux2014_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.9.0.dev20261120-cp312-cp312-manylinux2014_aarch64.whl
torchmonarch-0.9.0.dev20261120-cp312-cp312-macosx_11_0_universal2.whl CPython 3.12 CPython 3.12 macOS 11.0+ universal2 (ARM64, x86-64) Details for torchmonarch-0.9.0.dev20261120-cp312-cp312-macosx_11_0_universal2.whl
torchmonarch-0.9.0.dev20261120-cp311-cp311-manylinux2014_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.9.0.dev20261120-cp311-cp311-manylinux2014_x86_64.whl
torchmonarch-0.9.0.dev20261120-cp311-cp311-manylinux2014_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.9.0.dev20261120-cp311-cp311-manylinux2014_aarch64.whl
torchmonarch-0.9.0.dev20261120-cp311-cp311-macosx_11_0_universal2.whl CPython 3.11 CPython 3.11 macOS 11.0+ universal2 (ARM64, x86-64) Details for torchmonarch-0.9.0.dev20261120-cp311-cp311-macosx_11_0_universal2.whl

Total release size: 1.3 GB

Release files / torchmonarch-0.9.0.dev20261120-cp314-cp314t-manylinux2014_x86_64.whl

Download URL torchmonarch-0.9.0.dev20261120-cp314-cp314t-manylinux2014_x86_64.whl
Size 89.6 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
58b4971cd9fbffba1d2e4820c4b6a6a927ec0ff179f5298af6bbee83ab71656c
BLAKE2b-256 checksum
How to use checksums
f3cab03ed8c7a9af6ecf8956d68104fff93572bde45d4049f2f79fce72fd645c
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp314-cp314t-manylinux2014_aarch64.whl

Download URL torchmonarch-0.9.0.dev20261120-cp314-cp314t-manylinux2014_aarch64.whl
Size 94.5 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
27713caf084650d9f9e78065bf1449638ad355f8bb10378f3bacdafc0b1c36e8
BLAKE2b-256 checksum
How to use checksums
d780b4386ff78e382d7dbe87b802fed41b75bf7edc0f7984248fd6f5e5f52dd3
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp314-cp314t-macosx_11_0_universal2.whl

Download URL torchmonarch-0.9.0.dev20261120-cp314-cp314t-macosx_11_0_universal2.whl
Size 71.5 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
0abe09f157e91811dd14a4f3cf3865864be5b57f07e258ba85a81428824c5228
BLAKE2b-256 checksum
How to use checksums
38fddf0755bfd5c8515fa554031279a32479eaf5639579f412f4fe6f311da0ac
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp314-cp314-manylinux2014_x86_64.whl

Download URL torchmonarch-0.9.0.dev20261120-cp314-cp314-manylinux2014_x86_64.whl
Size 89.6 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
f85b1334b50b5245d7bdcb1e3cb4e12c80fee129872213635be851f51bcecce9
BLAKE2b-256 checksum
How to use checksums
cf52c6446047ccc8a0263e8d6abfa02e1b2fe1652b636d28ab4201b32b3b80ab
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp314-cp314-manylinux2014_aarch64.whl

Download URL torchmonarch-0.9.0.dev20261120-cp314-cp314-manylinux2014_aarch64.whl
Size 94.4 MB
Tags CPython 3.14 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
ed38a2577c69f1f3e019ad00807579df6d4c147d193cf156229368fe3c8cfeeb
BLAKE2b-256 checksum
How to use checksums
0e8afaab8d984f748867a2ebbb6b70086b0bf1bbc728c491850bc287c056360b
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp314-cp314-macosx_11_0_universal2.whl

Download URL torchmonarch-0.9.0.dev20261120-cp314-cp314-macosx_11_0_universal2.whl
Size 71.5 MB
Tags CPython 3.14 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
6cb8d9f23dcbbe28269ca8dcb545b4786cd3237678beae68cfc511fa1742fde2
BLAKE2b-256 checksum
How to use checksums
4e43284b36482094a1fe0e8f5449332a4779c37ad13e61754be1cf1829e2c4dd
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp313-cp313-manylinux2014_x86_64.whl

Download URL torchmonarch-0.9.0.dev20261120-cp313-cp313-manylinux2014_x86_64.whl
Size 89.6 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
6757e328cd17eb9b37e7f847ae125aa5595f8ce8f29a3fa891769d998f04c151
BLAKE2b-256 checksum
How to use checksums
fe0e1db60a18282207774c385f7bcf4e2fc6bca6b1706c16a21b75e2a03051ff
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp313-cp313-manylinux2014_aarch64.whl

Download URL torchmonarch-0.9.0.dev20261120-cp313-cp313-manylinux2014_aarch64.whl
Size 94.5 MB
Tags CPython 3.13 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
456d8faec79a67578b1c7589ba2658067b7674cb2adadf4b4ed8b260d11a7be9
BLAKE2b-256 checksum
How to use checksums
6069da38f4dea3f6fff31201979e4d4c6890a5d2c9df664fc40ba4837471bd5a
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp313-cp313-macosx_11_0_universal2.whl

Download URL torchmonarch-0.9.0.dev20261120-cp313-cp313-macosx_11_0_universal2.whl
Size 71.5 MB
Tags CPython 3.13 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
52f9d3b1bc85dc98d0857dc41b9ae167652768119a70684748fc8dc775dfa965
BLAKE2b-256 checksum
How to use checksums
fcb04fe4f4f51b5eeef8f8b4402bb1a02c092016bb459f6291ed8210f5fe403b
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp312-cp312-manylinux2014_x86_64.whl

Download URL torchmonarch-0.9.0.dev20261120-cp312-cp312-manylinux2014_x86_64.whl
Size 89.6 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
bc55e063bb6d99388b80a79e61f1dd2e62455f1afc78099068091f395318d429
BLAKE2b-256 checksum
How to use checksums
b5822d33d78c098b4229756e1cb64643aaeb5c6e13b51a2f0e1b2e90e8f66551
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp312-cp312-manylinux2014_aarch64.whl

Download URL torchmonarch-0.9.0.dev20261120-cp312-cp312-manylinux2014_aarch64.whl
Size 94.4 MB
Tags CPython 3.12 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
93721dcb9b36a3db15d53fc5a61869be5b884087a4d6f91ed3ff3f2dfe8046b4
BLAKE2b-256 checksum
How to use checksums
4bed28e39b9b1eed11dcfb80212e4e502956e1fd060accfe87721749ec9970d2
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp312-cp312-macosx_11_0_universal2.whl

Download URL torchmonarch-0.9.0.dev20261120-cp312-cp312-macosx_11_0_universal2.whl
Size 71.5 MB
Tags CPython 3.12 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
ff359e738d38c10b4d2a174446e9bde06d294c0297d46cb5871ba6b1328689a2
BLAKE2b-256 checksum
How to use checksums
47fdc7e47253fa29afb8343ae554053acbe3f9658df234262c78632770be29ef
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp311-cp311-manylinux2014_x86_64.whl

Download URL torchmonarch-0.9.0.dev20261120-cp311-cp311-manylinux2014_x86_64.whl
Size 89.6 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
78127194bc6379292257e1bb0e27c2305a38ea56bd96099f6e754b201d8c5f27
BLAKE2b-256 checksum
How to use checksums
3dee5da3c085bbcebe7f8020e91039c52ec71f3e3e41a66deddc5e625718892d
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp311-cp311-manylinux2014_aarch64.whl

Download URL torchmonarch-0.9.0.dev20261120-cp311-cp311-manylinux2014_aarch64.whl
Size 94.5 MB
Tags CPython 3.11 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
8f2a05dff46bc2042bce3e1c702c00bb533bbf78cf2f7357f349e3b014170d2c
BLAKE2b-256 checksum
How to use checksums
e8763df45cb3e399a54d52f76676527443d9a7c1a8b8705dc1837d34f96e1d75
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 20, 2026.

Transparency log

Release files / torchmonarch-0.9.0.dev20261120-cp311-cp311-macosx_11_0_universal2.whl

Download URL torchmonarch-0.9.0.dev20261120-cp311-cp311-macosx_11_0_universal2.whl
Size 71.5 MB
Tags CPython 3.11 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
57da9cab14dac6b2dcba60373c0963c7712edbeb4cf9645289ea7954130dad19
BLAKE2b-256 checksum
How to use checksums
5bea1cc29bf507edb7babb445e49e248a46acad950855220a2d94afa25cc598b
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 20, 2026.

Transparency log

Security for torchmonarch 0.9.0.dev20261120

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 torchmonarch-0.9.0.dev20261120-cp314-cp314t-manylinux2014_x86_64.whl

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 20, 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

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