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

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.dev20261119
File Actions
torchmonarch-0.9.0.dev20261119-cp314-cp314-manylinux2014_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.9.0.dev20261119-cp314-cp314-manylinux2014_x86_64.whl
torchmonarch-0.9.0.dev20261119-cp314-cp314-manylinux2014_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.9.0.dev20261119-cp314-cp314-manylinux2014_aarch64.whl
torchmonarch-0.9.0.dev20261119-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.dev20261119-cp314-cp314-macosx_11_0_universal2.whl
torchmonarch-0.9.0.dev20261119-cp313-cp313-manylinux2014_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.9.0.dev20261119-cp313-cp313-manylinux2014_x86_64.whl
torchmonarch-0.9.0.dev20261119-cp313-cp313-manylinux2014_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.9.0.dev20261119-cp313-cp313-manylinux2014_aarch64.whl
torchmonarch-0.9.0.dev20261119-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.dev20261119-cp313-cp313-macosx_11_0_universal2.whl
torchmonarch-0.9.0.dev20261119-cp312-cp312-manylinux2014_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.9.0.dev20261119-cp312-cp312-manylinux2014_x86_64.whl
torchmonarch-0.9.0.dev20261119-cp312-cp312-manylinux2014_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.9.0.dev20261119-cp312-cp312-manylinux2014_aarch64.whl
torchmonarch-0.9.0.dev20261119-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.dev20261119-cp312-cp312-macosx_11_0_universal2.whl
torchmonarch-0.9.0.dev20261119-cp311-cp311-manylinux2014_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.9.0.dev20261119-cp311-cp311-manylinux2014_x86_64.whl
torchmonarch-0.9.0.dev20261119-cp311-cp311-manylinux2014_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.9.0.dev20261119-cp311-cp311-manylinux2014_aarch64.whl
torchmonarch-0.9.0.dev20261119-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.dev20261119-cp311-cp311-macosx_11_0_universal2.whl

Total release size: 1.0 GB

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

Download URL torchmonarch-0.9.0.dev20261119-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
40d5cab967b18d167d1015a6e2c374288cb58cf7bc68a6a5cbf2228fcf2923c7
BLAKE2b-256 checksum
How to use checksums
cc50fbeb0d2aa6d8eb9caf8bcbded3503c7e15155eb44f6ac2a625b9ac87fcf6
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-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
5cb20ae86da6ebea990187b2d0076c075670e99df116e46a76f8ba775e7a4f7d
BLAKE2b-256 checksum
How to use checksums
69a17f84f235ed3ae33fd06d2a5c69fa7bc85118c12a4f66acdd49c549578d02
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-cp314-cp314-macosx_11_0_universal2.whl
Size 71.6 MB
Tags CPython 3.14 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
35edc88433bbf6b010ea6afaf8a09cc454872d2825778813b2f78d1bce6ca034
BLAKE2b-256 checksum
How to use checksums
d7079c8a630504da4dda5d55e1f8e3e72b2baf354b722d35ccee20299740d141
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-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
d753d509da09b98b4ade090951a8c1e470412fb07a6fb1ad0989b39890db0a11
BLAKE2b-256 checksum
How to use checksums
7bb24fcd10b78a033bb348ed7c7f9ea9cfd5b2509a16d2953bb65c8ed1349187
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-cp313-cp313-manylinux2014_aarch64.whl
Size 94.4 MB
Tags CPython 3.13 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
c3828cb7b7e05ffc9dfbd904d18b5574a4557217e3d65bdee3d16562f9bdf54b
BLAKE2b-256 checksum
How to use checksums
f8343c86da0b733aa187166e5b0572cc6a6fd1ca8e4d4c69372548c56705c561
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-cp313-cp313-macosx_11_0_universal2.whl
Size 71.6 MB
Tags CPython 3.13 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
ce3d13f9e4be39b59fedb17db51ae529eb8a2cdc3f1508c6e0c723799d7e4fc4
BLAKE2b-256 checksum
How to use checksums
007023efc1f6569f32f32ef881b1de255dcb09c3d00a90adb5341d7233839552
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-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
1ff0f3bf6c90966ac8a0ef62502641ab08ec289af8935d1048e4c5909207032f
BLAKE2b-256 checksum
How to use checksums
e9f67a45708aeebdc77fcdee3050a401d038221a41815d5557a0422ed90dff1f
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-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
d0842e6fc58b689092e6d5bd1a24f1a0a62b1a5f18549a97a4420d31b34dbbd2
BLAKE2b-256 checksum
How to use checksums
19f03fd940f7fa51602eb90554f5b705000f1745a2fa665c8563c1ca7d5f86a6
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-cp312-cp312-macosx_11_0_universal2.whl
Size 71.6 MB
Tags CPython 3.12 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
1775b2f2aac2d833fe82e38bbffa10c18543e0300c52c6968c557f681667f121
BLAKE2b-256 checksum
How to use checksums
46f6f90d3e67388e0b6875c232a1d94e749e1e22e89c65e0401d038427a9b47e
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-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
16ef733922eebde81268f812eb0ed227ef631eb4e2344e828db7aaa004975cc2
BLAKE2b-256 checksum
How to use checksums
8e8d24a1561dbd77ca1c26c9e33d1b93cac566799c178477ca0eee00a3836d29
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-cp311-cp311-manylinux2014_aarch64.whl
Size 94.4 MB
Tags CPython 3.11 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
86e52c3ea1a1be47241b4bcebf6f641aa42486ca9b102f520b1f1737a3b22347
BLAKE2b-256 checksum
How to use checksums
3eef9833625a14c046232e1a07fb2f2393eae0bf9a25b6deacb3c336d0a56da0
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 19, 2026.

Transparency log

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

Download URL torchmonarch-0.9.0.dev20261119-cp311-cp311-macosx_11_0_universal2.whl
Size 71.6 MB
Tags CPython 3.11 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
8ed635a3e95c173a06d62b73f97cde927d1f4709bca1c21e0d66c98e6314972a
BLAKE2b-256 checksum
How to use checksums
9d1c1e3ae9c392bf087365591337f17c4a6aed75553b2344c80d0786307147f8
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 19, 2026.

Transparency log

Security for torchmonarch 0.9.0.dev20261119

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

Select from 12 files

Attestation for torchmonarch-0.9.0.dev20261119-cp314-cp314-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 19, 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