Skip to main content

MORIE 森 morie hex logo

Multi-domain Open Research and Inferential Estimation.

A multi-domain scientific computing toolkit (Python and R) for observational inference, with sociolegal, signal-processing, cryptographic, spatial-statistics, statistical-physics, and psychometrics modules. Hosts the MRM framework as a primary application for Canadian carceral, police, and oversight data analysis.

The R package ships native causal-inference engines — matching (nearest/Mahalanobis/exact/CEM/optimal/genetic/cardinality), double machine learning with clustered SEs, R-learner causal forests, T/S/X/DR meta-learners, design-based GLM, and a causal DAG toolkit (morie_dag*) — implemented in-package and cross-validated against MatchIt, DoubleML, grf, and dagitty rather than depending on them.

CI CodeQL License: AGPL-3.0-or-later PyPI version rmorie on r-universe Python 3.10+ Website

The morie command line checks PyPI once a day for a newer release (fail-silent, cached); import morie makes no network request. Set MORIE_NO_UPDATE_CHECK=1 to disable it.

Installation

Full step-by-step install guide with platform-specific notes (PEP 668 on Debian, python 3.13 segfault on Raspberry Pi OS, etc.) is at INSTALLATION.md.

morie is a Python (and R) package — once Python is present it is pip install morie. If you are starting with nothing installed, INSTALLATION.md opens with Step 1 — install the prerequisites: every tool you might need (Python, curl, bash/WSL, Git Bash, winget, Homebrew, Docker, R) with its official download. The short version:

Two steps, whatever the channel. Install morie, then run

morie interactive install

once per user. The published package leaves out the five modules behind morie repl, morie exec, morie agent and morie tui (they run code you or a model type); that command fetches them for your installed version from the release tag on GitHub and checks each against the manifest inside the package. The one-liner installer below runs it for you. A verb that needs the layer says so and, on a terminal, offers to run it. Details: the interactive layer.

  • Windows — install Python from python.org (on the first screen tick Add python.exe to PATH), then pip install morie. Full walkthrough: Windows below. Windows has no curl/bash, so the one-liner does not apply there.
  • macOS / Linux — the one-liner below sets up everything. It needs curl and bash, which macOS has built in and most Linux ships.
  • Already have Python ≥3.10 — just pip install morie (on Debian, Ubuntu and Raspberry Pi OS use the venv three-liner below; their system pip refuses to install into /usr). The estimators take a pandas DataFrame, a CSV path, or a dict of columns; pandas is optional (morie ships its own frame core).

For terminal users — one-liner (Linux / macOS / WSL)

The simplest path if you have a terminal with curl and bash — both are built into macOS and preinstalled on most Linux (Windows has no bash, so use the installer above instead). It then bootstraps everything else for you: Python via uv, a managed venv, and the morie wheel. No pre-existing Python or pip needed.

curl -fsSL https://rootcoder007.github.io/morie/install.sh | bash

Or, with R alongside Python:

curl -fsSL https://rootcoder007.github.io/morie/install.sh | bash -s -- --auto

After install, ~/.local/bin/morie is a thin shim into the managed venv at ~/.venvs/morie. Full install instructions, channel comparison, and platform-specific notes are at rootcoder007.github.io/morie/#quick-start.

On minimal Linux containers (Alpine, slim Debian) that ship without curl, install it first: apt-get install -y curl or apk add curl. macOS already has curl built in.

Debian, Ubuntu, Raspberry Pi OS — plain pip in a venv

Debian-family systems mark the system Python "externally managed", so pip install morie stops with an error. A virtual environment is the supported way and needs nothing beyond the stock python3 (add sudo apt-get install -y python3-venv if venv is missing):

python3 -m venv ~/.venvs/morie
source ~/.venvs/morie/bin/activate
pip install -U morie
morie --version
morie interactive install

Activate the venv (source ~/.venvs/morie/bin/activate) in each new shell, or call ~/.venvs/morie/bin/morie directly.

Debian, Ubuntu, Fedora — apt / dnf

Debian, Ubuntu and Fedora can install the morie command (it lives in its own venv under /opt/morie) from the signed apt-morie repository, which also covers dnf4, RHEL and yum:

# Debian / Ubuntu
sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://rootcoder007.github.io/apt-morie/key.gpg \
  | sudo gpg --dearmor -o /etc/apt/keyrings/rootcoder007.gpg
echo "deb [signed-by=/etc/apt/keyrings/rootcoder007.gpg] https://rootcoder007.github.io/apt-morie/apt stable main" \
  | sudo tee /etc/apt/sources.list.d/morie.list
sudo apt update
sudo apt install morie

# Fedora 41+
sudo dnf config-manager addrepo --from-repofile=https://rootcoder007.github.io/apt-morie/rpm/morie.repo
sudo dnf install morie

Windows doesn't ship curl, bash, python, or R, so the Linux/macOS one-liner above won't run there. The path that works on any Windows with no prerequisites:

  1. Install Python from python.org/downloads — on the first installer screen, tick "Add python.exe to PATH" (skipping this is the No. 1 cause of python being "not recognized" in the terminal).
  2. (Optional — for the R package) install R from cran.r-project.org/bin/windows/base.
  3. Open PowerShell and install morie:
python -m pip install --upgrade pip
python -m pip install morie
python -c "import morie; print(morie.__version__)"
morie interactive install

For the R package, install rmorie (the R distribution of morie): Rscript -e "install.packages(c('rmoriebricklayer','rmoriedata','rmorie'), repos=c('https://rootcoder007.r-universe.dev','https://cloud.r-project.org'))"

Prefer a package manager? If winget --version works on your machine, winget install -e --id Python.Python.3.12 (and RProject.R) installs the prerequisites in one line each — but winget is absent from many Windows installs, so the installer steps above are the reliable default. The full Windows walkthrough, including fixes for common errors (python opening the Microsoft Store, PowerShell execution policy, long-path), is in INSTALLATION.md.

Python — Homebrew (macOS / Linuxbrew)

If you don't have Homebrew yet, install it first (macOS ships curl and bash, so this works out of the box):

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Then:

brew tap rootcoder007/morie
brew install morie
morie interactive install

The tap repo is rootcoder007/homebrew-morie. It pulls morie's source distribution from PyPI and bundles a self-contained python@3.12 venv — no system Python required.

Python — PyPI (manual; requires pip already installed)

pip install morie
morie interactive install

Heads-up: Debian, Ubuntu and Raspberry Pi OS forbid pip outside a virtual environment (PEP 668). Use the venv three-liner above, or the one-liner installer, which sets one up for you. morie needs no NumPy or SciPy, so no compiled scientific stack has to be present.

Python — Docker (no local dependencies)

# Latest stable
docker run --rm ghcr.io/rootcoder007/morie:latest morie --help

# Pin to a specific version (recommended for reproducibility)
docker run --rm ghcr.io/rootcoder007/morie:1.5.2 morie --help

Published on every release with a versioned tag, a major.minor tag and :latest (linux/amd64). Requires only Docker — no Python, no pip.

The interactive layer — morie repl, morie exec, morie agent, morie tui

Every channel above leaves five modules out on purpose: they execute code that you or a model type, and package scanners flag that surface. Add them for your user in one step (the one-liner installer does it for you; a verb that needs them prints this command and, on a terminal, offers to run it):

morie interactive install

That fetches the files for your installed version from the tagged source on GitHub, checks each one against the SHA-256 manifest shipped inside the package, and stores them under ~/.local/share/morie/interactive (%LOCALAPPDATA%\morie\interactive on Windows). Nothing in site-packages changes. morie interactive status shows what is active and morie interactive remove takes it out again. The TUI also needs pip install "morie[interactive]". A source checkout has all of this already. Offline: morie interactive install --from path/to/morie/src/morie.

R package: rmorie — r-universe

The R distribution of morie is the rmorie package.

# rmorie and its companions rmoriebricklayer and rmoriedata all come from
# r-universe (prebuilt binaries for macOS and Windows, source on Linux). CRAN
# carries older companions, so name them: pak upgrades named packages to the
# current release, replacing an older copy already installed.
if (!requireNamespace("pak", quietly = TRUE)) {
  install.packages("pak", repos = "https://cloud.r-project.org")
}
pak::repo_add(rootcoder007 = "https://rootcoder007.r-universe.dev")
pak::pkg_install(c("rmoriebricklayer", "rmoriedata", "rmorie"))

From a terminal (single quotes outside, double quotes inside, so the shell passes the R code through untouched):

Rscript -e 'if (!requireNamespace("pak", quietly = TRUE)) install.packages("pak", repos = "https://cloud.r-project.org"); pak::repo_add(rootcoder007 = "https://rootcoder007.r-universe.dev"); pak::pkg_install(c("rmoriebricklayer", "rmoriedata", "rmorie"))'
# without pak (keep repos: Rscript has no mirror chooser)
Rscript -e 'install.packages(c("rmoriebricklayer", "rmoriedata", "rmorie"), repos = c("https://rootcoder007.r-universe.dev", "https://cloud.r-project.org"))'

On macOS, CRAN's R (from https://cloud.r-project.org/bin/macosx/) installs r-universe's prebuilt binaries in seconds. Homebrew's R cannot use them, so there every package is compiled from source.

The same R code also lives in this repository as r-package/morie (package name morie), tracking every commit here; build it from source (needs a C++ toolchain):

Rscript -e 'if (!requireNamespace("pak", quietly = TRUE)) install.packages("pak", repos = "https://cloud.r-project.org"); pak::repo_add(rootcoder007 = "https://rootcoder007.r-universe.dev"); pak::pkg_install(c("rmoriebricklayer", "rmoriedata", "rootcoder007/morie/r-package/morie@v1.4.5"))'
# without pak
Rscript -e 'repos <- c("https://rootcoder007.r-universe.dev", "https://cloud.r-project.org"); install.packages(c("rmoriebricklayer", "rmoriedata", "remotes"), repos = repos); remotes::install_github("rootcoder007/morie@v1.4.5", subdir = "r-package/morie", repos = repos, upgrade = "always")'

Or let morie run either install for you: morie r-install (r-universe) or morie r-install --github (this repository's R arm).

Quick start

import morie
from morie.data import load_dataset

# CPADS 2021-22 public-use microdata (40,931 rows): downloaded from
# open.canada.ca on first use (about a minute), then served from the
# local cache in ~/.cache/morie
df = load_dataset("ocp21")
print(df.shape)

# Welch's two-sample t-test, and the guide every morie.fn callable carries
from morie.fn import describe, welcht

result = welcht([5.1, 4.9, 5.6, 5.8, 6.0], [6.2, 6.8, 7.1, 6.5, 7.4])
print(result)
print(describe("welcht"))

From the terminal

Every feature is a verb of the morie command; morie --help lists them, morie cheatsheet fits them on one page, and the R package ships the same verbs as rmorie (see below).

morie list-modules                                   # the 23 analysis modules
morie run-module power-design --output-dir out/      # one module, its tables as CSV
morie explain power_two_proportion_gender.csv        # how to read an output table
morie list-datasets                                  # 71 catalog keys + the curated tables after login
morie pull ocp21 --out cpads.csv                     # the real CPADS PUMF, cached; modules use it from then on
morie pull --all --out datasets/                     # every catalog dataset
morie login                                          # the data key for data.rmorie.com: GitHub sign-in
morie login --email you@example.com                  # an emailed code instead: type it at the prompt
morie login --token                                  # a key you were given
morie login --no-browser                             # server / SSH / no browser: prints a link + code for any device
morie pull chicago_crime/incidents --out incidents.csv   # a curated table (8.6M rows)
morie config setup                                   # bring a model: a provider key, your own server, or Ollama
morie ask "which module fits a treatment-control design?"
morie emissions --seconds 5 --country CAN            # energy + CO2 of this machine, sealed in a capsule
morie pipeline --modules power-design -y             # modules + emissions tracking + capsule
morie verify-pollution --pollutant no2 --demo        # pollution -> health causal pipeline
morie selftest                                       # every subsystem, offline (no downloads)

Where the datasets come from

morie list-datasets prints a Route column next to every key. Of the 71 keys, 70 download themselves on first use and are cached: open.canada.ca (CPADS, CSADS, CSUS microdata and bootstrap weights), data.ontario.ca (the OTIS correctional tables and institution locations), Statistics Canada (CCHS), CIHI (the indicator library and its tables), Environment Canada's NAPS air-quality files, the Toronto Police ArcGIS feeds (the Canada-wide NAPS hourly keys are about 2 million rows: allow ten minutes and 1.5 GB), the Health Infobase tables from health-infobase.canada.ca with the data.rmorie.com copy as the fallback, the OTIS research environments from data.rmorie.com (R objects: rmorie loads them, morie saves them for R), and the reviewed SIU corpus from the rmoriedata package on CRAN (fetched as a source tarball, no R needed). One key, the MAPQ workbook, is your own file: put it under a data directory and point MORIE_DATA_DIR at it, keeping the relative path that morie list-datasets shows. The curated tables at data.rmorie.com join the list once a key (issued on request at https://rmorie.com/access) is stored with morie login --token.

from morie.data import list_rmoriedata, load_rmoriedata
[r["slug"] for r in list_rmoriedata()]        # 99 tables + 8 data dictionaries
siu = load_rmoriedata("siu_directors_reports")  # 5,157 reviewed SIU reports

Beyond the catalog, the project keeps 160 databases materialised from Google BigQuery public datasets, plus the Health Infobase tables and the OTIS research files (Chicago crime, EPA air quality, US census, FEC, FDA, NOAA, NHTSA, Hacker News, Ethereum, World Bank, ...), served from the edge at https://data.rmorie.com and opened by the key morie login --token stores (issued on request at https://rmorie.com/access, under https://rmorie.com/data-license). morie list-datasets shows their db/table keys with the route "data.rmorie.com"; morie pull db/table and load_dataset("db/table") fetch one (cached locally), and https://data.rmorie.com/browse runs SQL on any of them in the browser. They are rebuilt weekly without any project machine in the loop.

The R side has every verb

rmorie (r-universe) ships the same command line: rmorie::install_cli() puts rmorie on your PATH, and rmorie pull ocp21, rmorie run-module, rmorie emissions, rmorie verify-pollution, rmorie provider set, rmorie selftest and the rest behave like their morie twins. The two packages share the credentials file, the CPADS resolution order, the emissions CSV layout and the capsule format, so they mix in one workflow. morie r-install installs the R side from Python.

Data capsules

morie.capsule (write, verify, sign, bundle, drift, manifest, compare, ...) and morie capsule init|pin|verify|keygen|sign|drift author and check capsules in the rmoriebricklayer / rmbl-action format. Their twins in rmorie are morie_capsule_write() and so on: the same words name the same things: write/verify/sign/bundle/drift/manifest/compare take the same arguments and defaults, return the same fields, and verification gives the same check rows (those of rmoriebricklayer::vrfcps()). Both sign with hmac (a shared secret), ML-DSA (ML-DSA-44, ML-DSA-65, ML-DSA-87) and XMSS (xmss-sha256) keys, byte-compatible either way (morie capsule keygen --scheme ML-DSA-65 --out key.json, then morie capsule sign DIR --scheme ML-DSA-65 --key-file key.json). The deliberate differences: morie's sign() and bundle() have no deterministic, and SLH-DSA keys sign only in rmorie; rmorie's results checks are a data frame, morie's a list of dicts; rmorie's drift takes the capsule directory (dir) and a data frame or CSV as current, morie's takes ref (a capsule directory or a CSV) and a CSV; rmorie pins only a CSV, morie any file (a row count for a CSV); morie also has load, pin, record, canon, digest and the attestation helpers, which in R are rmoriebricklayer's own (loadprov(), recrd(), mnfcanon(), mnfdgst(), cpsatst()); and the command line morie capsule init|pin|verify|sign|drift exits 0 (verified, no drift), 1 (a check failed or drift) or 2 (an error), where the R functions return a result with $ok (or $anydrft) and stop on an error.

What's new

Per-release user-facing changes are now in WHATS_NEW.md. For the R-package changelog see r-package/morie/NEWS.md. For the planned roadmap see ROADMAP.md.

Documentation

Full documentation is at rootcoder007.github.io/morie.

  • Website: https://rmorie.com — the MORIE family (rmorie, morie, rmoriebricklayer, rmoriedata) in one place.
  • Curated data: https://data.rmorie.com — the curated tables, opened by a personal data key (morie login: GitHub or an emailed code; or ask at https://rmorie.com/access), each checked against its SHA-256; /browse for SQL in the browser.
  • CLI reference: cli; learn pages for datasets, emissions and capsules and the R command line.
  • Language models: none are hosted; bring your own. morie ask uses your own OpenAI-compatible server, then a provider whose key is set (OpenAI, Anthropic, Google Gemini, OpenRouter, Groq, Mistral and more, 16 in all), then an Ollama server (ollama serve); morie config setup walks through it and morie doctor says which route answers. The same settings file serves rmoriebricklayer's rmbl config. See the language-model docs.

Citation

If you use morie in your research, please cite the software:

Ruhela, V. S. (2026). morie: Multi-domain Open Research and Inferential Estimation. https://github.com/rootcoder007/morie

BibTeX:

@Manual{ruhela_morie_2026,
  title  = {morie: Multi-domain Open Research and Inferential Estimation},
  author = {Vansh Singh Ruhela},
  year   = {2026},
  url    = {https://github.com/rootcoder007/morie},
}

The single citation above covers both the R (r-package/morie/) and Python (src/morie/) implementations, which ship under the same version.

See CITATION.cff for machine-readable citation metadata (BibTeX, etc.) — that file is what GitHub's "Cite this repository" button consumes.

Acknowledgments

AI assistance

MORIE was developed with substantial assistance from frontier AI assistants. The author retains full responsibility for the code, the methods, and the scientific claims; AI assistance accelerated implementation but does not change the attribution of the work.

  • Claude — Anthropic. Anthropic's Claude family (Opus, Sonnet, and Haiku across the 4.x and 5.x generations) was used extensively throughout development for code generation, refactoring, documentation, code review, and design discussions. Use was supported by Anthropic research-credit programs.

  • Gemini and Vertex AI — Google. Google's Gemini 2.5 models (Pro and Flash) on the Vertex AI platform were used extensively for additional code generation, cross-checking Claude-generated code, multi-modal data analysis, and prototype evaluation. Use was supported by Google research-credit programs.

Funding and infrastructure

  • Anthropic — Claude API research credits.
  • Google — Gemini / Vertex AI research credits.

Data acknowledgments

Several MRM analyses use Statistics Canada and Health Canada Public Use Microdata Files (PUMFs) — including the Canadian Cannabis Survey (CCS), the Canadian Student Alcohol and Drugs Survey (CSADS), the Canadian Substance Use Survey (CSUS), the Canadian Alcohol and Drugs Survey (CADS), and the Canadian Postsecondary Education Alcohol and Drug Use Survey (CPADS) — along with Public Health Agency of Canada (PHAC) and Canadian Institute for Health Information (CIHI) aggregates. Although the analyses use Statistics Canada and Health Canada data, the analyses, interpretations, and conclusions are those of the author and do not represent the views of Statistics Canada or Health Canada. Ontario open data (OTIS, A01-RCDD release; via data.ontario.ca) and Toronto Police Service open data are used under the same standard disclaimer.

License

morie is licensed under the GNU Affero General Public License, version 3.0 or later (AGPL-3.0-or-later), on both the Python and R sides. The AGPL is a strong copyleft license: anyone who distributes a modified morie — or offers a modified morie to users over a network — must publish their source. Modifications and improvements cannot be kept secret or taken closed-source.

  • Python and R packages (src/morie/, r-package/morie/) — AGPL-3.0-or-later. See LICENSE.
  • Optional Linux kernel adjuncts (kernel-module/morie.c, daemon/morie_lsm.py) — GPL-2.0-only (the Linux kernel ABI requires GPL for loaded modules). These are NOT part of the R / Python distribution; they are separately-licensed, independently-distributed adjuncts. See kernel-module/LICENSE-GPL2.
  • Papers, data and documentation — CC BY-NC-SA 4.0 (Creative Commons Attribution-NonCommercial-ShareAlike) unless explicitly marked otherwise.

Full detail in LICENSING.md.

Trust model — what the powerful features can do to your machine

morie is a developer/research toolkit with some intentionally powerful surfaces. They run local, user-supplied input by design — the only network-supplied code is the verified interactive layer below — but under an untrusted-input threat model each is high-impact, so every one defaults to the safe behaviour and gates the risky path behind a single, named, off-by-default environment knob:

Surface What it can do Safe default → opt-in
MORIE_NO_EXEC master kill-switch for all dynamic execution executes; set MORIE_NO_EXEC=1 to disable REPL/exec/shell everywhere
morie tui / polyglot REPLs run Python/R/shell/other code you type, like any REPL run your input only; honour MORIE_NO_EXEC=1. Feed them only code you'd run at your own shell
morie interactive install fetches the REPL/exec/agent/TUI modules (five files) from this version's release tag on GitHub, the one network-supplied code path every file is checked against the SHA-256 manifest shipped inside the package before it is enabled; nothing runs during the install; --no-verify is the opt-in for a non-release --ref
pt2gguf / morie convert-checkpoint deserialize .pt/.pkl model files refuses every checkpoint unless MORIE_TRUST_CHECKPOINT=1; even then the native reader only resolves tensors, storages and plain containers (the torch.load(weights_only=True) allowlist) and refuses any other object. Use checkpoints you produced or fully trust
bin/morie installer — Ollama remote install.sh fetched to a temp file with its SHA256 printed; executes only under MORIE_ALLOW_REMOTE_INSTALL=1
bin/morie — ESML_RC config shell config sourced on every run (persistence) not sourced unless MORIE_ALLOW_RC=1
bin/morie — morie cron writes your crontab (persistence) add/remove refuse unless MORIE_ALLOW_CRON=1; list is read-only
bin/morie — backup restore extracts a tar archive archives with absolute or .. paths are refused before extraction

morie doctor prints the current state of every knob so you can see the active trust posture at a glance. Only enable a knob for inputs you fully control.

Reporting issues / security

Metadata

Release files for morie 1.5.2

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

Source distribution (sdist)

Source distribution for morie 1.5.2
File Size Uploaded Provenance Actions
morie-1.5.2.tar.gz 15.7 MB With provenance Details for morie-1.5.2.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for morie 1.5.2
File Actions
morie-1.5.2-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for morie-1.5.2-cp314-cp314-win_amd64.whl
morie-1.5.2-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for morie-1.5.2-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
morie-1.5.2-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for morie-1.5.2-cp314-cp314-macosx_11_0_arm64.whl
morie-1.5.2-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for morie-1.5.2-cp313-cp313-win_amd64.whl
morie-1.5.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for morie-1.5.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
morie-1.5.2-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for morie-1.5.2-cp313-cp313-macosx_11_0_arm64.whl
morie-1.5.2-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for morie-1.5.2-cp312-cp312-win_amd64.whl
morie-1.5.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for morie-1.5.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
morie-1.5.2-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for morie-1.5.2-cp312-cp312-macosx_11_0_arm64.whl
morie-1.5.2-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for morie-1.5.2-cp311-cp311-win_amd64.whl
morie-1.5.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for morie-1.5.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
morie-1.5.2-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for morie-1.5.2-cp311-cp311-macosx_11_0_arm64.whl
morie-1.5.2-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for morie-1.5.2-cp310-cp310-win_amd64.whl
morie-1.5.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for morie-1.5.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
morie-1.5.2-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for morie-1.5.2-cp310-cp310-macosx_11_0_arm64.whl

Total release size: 185.3 MB

Release files / morie-1.5.2.tar.gz

Download URL morie-1.5.2.tar.gz
Size 15.7 MB
Tags Source
SHA-256 checksum
How to use checksums
92e42e2523d31384e19847702dfaddfd5eed480dd4122c5d7573f029d8a4ffea
BLAKE2b-256 checksum
How to use checksums
3c4ca1f7aeefb898fcc9dfbd3f3ccb75d03725c3793c724d411e205233edfb6e
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp314-cp314-win_amd64.whl

Download URL morie-1.5.2-cp314-cp314-win_amd64.whl
Size 11.5 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
489e8aa497240592eddd6845f58a063a4198260ca7d47fe4e2e3c513c0cb471f
BLAKE2b-256 checksum
How to use checksums
5618934e91e115434794d8292131fa681c712fa2337b957dea6d4ce455498975
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL morie-1.5.2-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 11.2 MB
Tags CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
00fb94a180097120379179e90a055f369dd64b90446533b9f605211e6fe25931
BLAKE2b-256 checksum
How to use checksums
f14253c64d8a963e7a629c0ff09f18c2c08b9d1d1f3cbb569bf8005068d516a2
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp314-cp314-macosx_11_0_arm64.whl

Download URL morie-1.5.2-cp314-cp314-macosx_11_0_arm64.whl
Size 11.2 MB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
2ee2c1c8c3c98f6f2af1f6c727e7783205f09ec96c8a641a82806e1ee5a65bf1
BLAKE2b-256 checksum
How to use checksums
a1ee10f09c09b24dd4c5ad504a5d6a4cbbe5cf8a051c9ba9346d30612725319d
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp313-cp313-win_amd64.whl

Download URL morie-1.5.2-cp313-cp313-win_amd64.whl
Size 11.5 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
20ead37d762ace812e182c7385a15c41845409b292ac871fb0ed45ee1358af95
BLAKE2b-256 checksum
How to use checksums
903edc82a5fa12ba39c6aabc3b1d4f0a3491a0abbb77a64f943f4d612b5a54d3
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL morie-1.5.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 11.2 MB
Tags CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
6e27a1abbf127e5329113e9307206b320e96cd4ba780762751b544e0e415af25
BLAKE2b-256 checksum
How to use checksums
18b496111d8e5fffff683a33730960794b7ff3e8e85cf72bf03dea787a0e0d94
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp313-cp313-macosx_11_0_arm64.whl

Download URL morie-1.5.2-cp313-cp313-macosx_11_0_arm64.whl
Size 11.2 MB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
84f6ca2eabcd3274c0365adbefac7ceed86dc7fb96692ff0b942dd92c4a162a8
BLAKE2b-256 checksum
How to use checksums
733b2b7bde3608f55934c6908245f08107bd638cfe3fee93ecab24cea75837bf
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp312-cp312-win_amd64.whl

Download URL morie-1.5.2-cp312-cp312-win_amd64.whl
Size 11.5 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
9ead650d60a26164d6df2c04d20d6e1e31beeadc5ddc22e03f081979ae0e9459
BLAKE2b-256 checksum
How to use checksums
814560693e5befbaf8c5a230a793f427b341a99fbe6204aa2a9030736eff804c
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL morie-1.5.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 11.2 MB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
f2b6a7c2fb4c717412b550cbd12662a17c9e184b6e500e5e56647b7438f437bc
BLAKE2b-256 checksum
How to use checksums
b7817d476e03f0bd24bccc01a9ca31ae6602625e39a8732920646ae390428e99
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp312-cp312-macosx_11_0_arm64.whl

Download URL morie-1.5.2-cp312-cp312-macosx_11_0_arm64.whl
Size 11.2 MB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
354129b4d3ec870a6a26e5b28419059026a399b8f4fd3350d9bdcc003adeba45
BLAKE2b-256 checksum
How to use checksums
f17dee1ca576876e96463aa365eea70d0c9088462704c0c4ef982f741d0207bc
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp311-cp311-win_amd64.whl

Download URL morie-1.5.2-cp311-cp311-win_amd64.whl
Size 11.5 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
7eba3cf71de5c7aa103e09964fe2614d0a99ac097be7afb762731fc6220f7e8a
BLAKE2b-256 checksum
How to use checksums
3a4d9794c6e0e8b328b8ea5dab4d886dc88f0885c7c368567f0b722bfb06f4fd
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL morie-1.5.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 11.2 MB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
abfe8ea5218a2f872f2b5bfb47e326c6cc7d80e003653e2c03a2d3ff956199db
BLAKE2b-256 checksum
How to use checksums
3092e559e4959a6411fd561b0661edcbc2fd97712927a183bd04297c17c483e4
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp311-cp311-macosx_11_0_arm64.whl

Download URL morie-1.5.2-cp311-cp311-macosx_11_0_arm64.whl
Size 11.2 MB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
4b3da8265f679600d5e5a058d5f9ae1afa610bd5ab741977cea79cbb089a6a46
BLAKE2b-256 checksum
How to use checksums
f3c2825893c90924907674811f60acbc4e97c2e2b47aa596e724b7e9c413117a
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp310-cp310-win_amd64.whl

Download URL morie-1.5.2-cp310-cp310-win_amd64.whl
Size 11.5 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
a30b22dbe813cc4e0224eb6e48705fe3ebf6e3afde464edfa17d7bcf5a94b4d2
BLAKE2b-256 checksum
How to use checksums
83987754fe6863c2b6caa3d8c577e8850e1a8b6fa39d61cb495dc17a1f5ec72d
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL morie-1.5.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 11.2 MB
Tags CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
38fcb3de9784018c42c975d5d574e1e27c21c4ff384c2f18a8ea0f65c57306a4
BLAKE2b-256 checksum
How to use checksums
039c556c446707aad17307e6fbfc3beb1b8482395d0b442e64739b267f998125
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 Oct 31, 2026.

Transparency log

Release files / morie-1.5.2-cp310-cp310-macosx_11_0_arm64.whl

Download URL morie-1.5.2-cp310-cp310-macosx_11_0_arm64.whl
Size 11.2 MB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
15e5b03cf694115f9d51bad95de0f32df71a9a941364f79a8ad0450ebd4c01dc
BLAKE2b-256 checksum
How to use checksums
4256243a86cd5ac9586436bc5ef0e11df6afb72d7fdd3e7d3c4037f617f5c67a
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 Oct 31, 2026.

Transparency log

Security for morie 1.5.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 16 files in this release have been uploaded with provenance metadata.

Select from 16 files

Attestation for morie-1.5.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.5.2 This release

16 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page