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.8.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.8.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.8.0.dev20261112

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.8.0.dev20261112
File Actions
torchmonarch-0.8.0.dev20261112-cp314-cp314-manylinux2014_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.8.0.dev20261112-cp314-cp314-manylinux2014_x86_64.whl
torchmonarch-0.8.0.dev20261112-cp314-cp314-manylinux2014_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.8.0.dev20261112-cp314-cp314-manylinux2014_aarch64.whl
torchmonarch-0.8.0.dev20261112-cp314-cp314-macosx_11_0_universal2.whl CPython 3.14 CPython 3.14 macOS 11.0+ universal2 (ARM64, x86-64) Details for torchmonarch-0.8.0.dev20261112-cp314-cp314-macosx_11_0_universal2.whl
torchmonarch-0.8.0.dev20261112-cp313-cp313-manylinux2014_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.8.0.dev20261112-cp313-cp313-manylinux2014_x86_64.whl
torchmonarch-0.8.0.dev20261112-cp313-cp313-manylinux2014_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.8.0.dev20261112-cp313-cp313-manylinux2014_aarch64.whl
torchmonarch-0.8.0.dev20261112-cp313-cp313-macosx_11_0_universal2.whl CPython 3.13 CPython 3.13 macOS 11.0+ universal2 (ARM64, x86-64) Details for torchmonarch-0.8.0.dev20261112-cp313-cp313-macosx_11_0_universal2.whl
torchmonarch-0.8.0.dev20261112-cp312-cp312-manylinux2014_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.8.0.dev20261112-cp312-cp312-manylinux2014_x86_64.whl
torchmonarch-0.8.0.dev20261112-cp312-cp312-manylinux2014_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.8.0.dev20261112-cp312-cp312-manylinux2014_aarch64.whl
torchmonarch-0.8.0.dev20261112-cp312-cp312-macosx_11_0_universal2.whl CPython 3.12 CPython 3.12 macOS 11.0+ universal2 (ARM64, x86-64) Details for torchmonarch-0.8.0.dev20261112-cp312-cp312-macosx_11_0_universal2.whl
torchmonarch-0.8.0.dev20261112-cp311-cp311-manylinux2014_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64 Details for torchmonarch-0.8.0.dev20261112-cp311-cp311-manylinux2014_x86_64.whl
torchmonarch-0.8.0.dev20261112-cp311-cp311-manylinux2014_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64 Details for torchmonarch-0.8.0.dev20261112-cp311-cp311-manylinux2014_aarch64.whl
torchmonarch-0.8.0.dev20261112-cp311-cp311-macosx_11_0_universal2.whl CPython 3.11 CPython 3.11 macOS 11.0+ universal2 (ARM64, x86-64) Details for torchmonarch-0.8.0.dev20261112-cp311-cp311-macosx_11_0_universal2.whl

Total release size: 1.1 GB

Release files / torchmonarch-0.8.0.dev20261112-cp314-cp314-manylinux2014_x86_64.whl

Download URL torchmonarch-0.8.0.dev20261112-cp314-cp314-manylinux2014_x86_64.whl
Size 93.8 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
2515e34c9ac8113c993474b6bc54322854ac4b3ec041271f8782dfec1979b78c
BLAKE2b-256 checksum
How to use checksums
26904759077dba063413ee14f5e0e60cdb94ab0ab998e6261ea78bdeefe0d98b
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp314-cp314-manylinux2014_aarch64.whl

Download URL torchmonarch-0.8.0.dev20261112-cp314-cp314-manylinux2014_aarch64.whl
Size 99.1 MB
Tags CPython 3.14 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
be852c73ce01c166b84c78c872734697b26eea6d1ee496c954df59dc148881c1
BLAKE2b-256 checksum
How to use checksums
8f95d19950b62cad70872ed6f92d167d699a47053ed3c661297d605b54a1f768
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp314-cp314-macosx_11_0_universal2.whl

Download URL torchmonarch-0.8.0.dev20261112-cp314-cp314-macosx_11_0_universal2.whl
Size 74.5 MB
Tags CPython 3.14 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
dbae1af4bedebb38afc1148cfe2265940f22a1f7215d7682048da509196c7a9c
BLAKE2b-256 checksum
How to use checksums
c96dc2c736a76be6ed817feaf23c8e1e95eee76704b658db6a4810b45593ab54
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp313-cp313-manylinux2014_x86_64.whl

Download URL torchmonarch-0.8.0.dev20261112-cp313-cp313-manylinux2014_x86_64.whl
Size 93.7 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
dc5dd9c5373803d29c65b87a033fe0aed6939bcabf55d2462baf3c2ee7c881c0
BLAKE2b-256 checksum
How to use checksums
1c85f79e6499bda6f6c319afccb45c2d64a62e8399ddd313f786dc300252d719
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp313-cp313-manylinux2014_aarch64.whl

Download URL torchmonarch-0.8.0.dev20261112-cp313-cp313-manylinux2014_aarch64.whl
Size 99.1 MB
Tags CPython 3.13 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
8ff536baa2efe7a2bcad51553cfa2b4289679710138e81d320aaa29765745d04
BLAKE2b-256 checksum
How to use checksums
993a5b470a0bcd100328d2f7742f392f26e08424bd98b7705e7451601ef39dbb
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp313-cp313-macosx_11_0_universal2.whl

Download URL torchmonarch-0.8.0.dev20261112-cp313-cp313-macosx_11_0_universal2.whl
Size 74.6 MB
Tags CPython 3.13 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
f5893c61447551d561c5b0ae2d00e1b980f402e6e8d363e27e5ebf8b1a340364
BLAKE2b-256 checksum
How to use checksums
53357bbab51a6c89215c4deb379d8c231d2136e090594450a2d98c01eb482646
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp312-cp312-manylinux2014_x86_64.whl

Download URL torchmonarch-0.8.0.dev20261112-cp312-cp312-manylinux2014_x86_64.whl
Size 93.7 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
6fb1c47649e4df4b3e0a6ebe81d42713a653bb7b26fd6cf048aceeac63751027
BLAKE2b-256 checksum
How to use checksums
271497d345fdce007c5a5e6dc172ac64bf04e11dd0ad0b04b30b77186f75a43a
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp312-cp312-manylinux2014_aarch64.whl

Download URL torchmonarch-0.8.0.dev20261112-cp312-cp312-manylinux2014_aarch64.whl
Size 99.1 MB
Tags CPython 3.12 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
03a9f51a2e7ea85d66436d9af2453a09842ac7c4d2421c3ec97d52b745391933
BLAKE2b-256 checksum
How to use checksums
bb2b666f9559c82fecbfd528bb78e2774bc59d02352f2975a2f5f4c97295f165
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp312-cp312-macosx_11_0_universal2.whl

Download URL torchmonarch-0.8.0.dev20261112-cp312-cp312-macosx_11_0_universal2.whl
Size 74.6 MB
Tags CPython 3.12 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
12f29d90f605129c13f2b758c7a1e49f1c488711ac0e48f78f3f1f54f61d4dd6
BLAKE2b-256 checksum
How to use checksums
5aaa1319dba64dc6532ab7c467dbe841defb361632aa48003eb1e40ceb763705
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp311-cp311-manylinux2014_x86_64.whl

Download URL torchmonarch-0.8.0.dev20261112-cp311-cp311-manylinux2014_x86_64.whl
Size 93.8 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
ac65b50b4aaefe5246fce140a813684d5a7787c02bf90e6b9f78caa28bdec5e8
BLAKE2b-256 checksum
How to use checksums
5e6fc94bc75e02cea789040076de3d760e3681444d954251865251f5d905d7be
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp311-cp311-manylinux2014_aarch64.whl

Download URL torchmonarch-0.8.0.dev20261112-cp311-cp311-manylinux2014_aarch64.whl
Size 99.2 MB
Tags CPython 3.11 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
d856ed53942f4ec80700047d99eeafa6628a4e8d224cff992d39ef3a69854039
BLAKE2b-256 checksum
How to use checksums
7bf73210328ad9b749a8b59ba2cf52a60fbbd84275fc80056b35b1c04b825f50
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 12, 2026.

Transparency log

Release files / torchmonarch-0.8.0.dev20261112-cp311-cp311-macosx_11_0_universal2.whl

Download URL torchmonarch-0.8.0.dev20261112-cp311-cp311-macosx_11_0_universal2.whl
Size 74.6 MB
Tags CPython 3.11 macOS 11.0+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
b2a153e2b4c80afb159ab634749364ba00483b971efa54efc010e612a9529e63
BLAKE2b-256 checksum
How to use checksums
80b34d76fc26b69d171162a8391878c4d89bc87b6319f9512efb330e23db8a71
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 12, 2026.

Transparency log

Security for torchmonarch 0.8.0.dev20261112

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.8.0.dev20261112-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 12, 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