pysafe-pickle
Safe, fast, schema-evolvable Python object graph serialization powered by Rust.
Features
- Drop-in pickle API —
dumps/loads/dump/loadwith the same signatures - Zero arbitrary code execution — no
__reduce__or__setstate__calls during deserialization - Schema versioning — migration hooks for evolving your data models
- Zero-copy tensor support — NumPy and PyTorch integration
- Rust-native performance — PyO3 bindings for speed
- Pickle-compatible streaming —
Pickler/Unpicklerclasses,PickleBuffer(PEP 574) - HMAC integrity — optional tamper detection on serialized data
Installation
pip install pysafe-pickle
For tensor support:
pip install pysafe-pickle[numpy]
pip install pysafe-pickle[torch]
pip install pysafe-pickle[all]
Quick Start
import pysafe_pickle as psp
# Serialize
data = {"key": "value", "numbers": [1, 2, 3]}
encoded = psp.dumps(data)
# Deserialize
decoded = psp.loads(encoded)
assert decoded == data
Schema Evolution
Define versioned dataclasses and register migrations:
from dataclasses import dataclass
import pysafe_pickle as psp
@dataclass
class User:
name: str
age: int
email: str = ""
__pysafe_pickle_version__ = 2
@psp.migrate(from_version=1, to_version=2, type_name="User")
def migrate_v1_to_v2(state: dict) -> dict:
"""V1 had 'name' + 'age', V2 adds 'email'."""
state["email"] = ""
state["__pysafe_pickle_version__"] = 2
return state
How it works
- Set
__pysafe_pickle_version__as a class attribute on your dataclass (legacy__pygraph_version__is also fully supported) - Register migration functions with
@psp.migrate(from_version=N, to_version=M, type_name="ClassName") - Migration functions receive a
dictof the old state and return adictwith the new state - Chains of migrations are resolved automatically (e.g., v1 → v2 → v3)
Pickler / Unpickler
Use pickle-compatible streaming classes:
import pysafe_pickle as psp
import io
# Streaming dump
buf = io.BytesIO()
pickler = psp.Pickler(buf, protocol=5)
pickler.dump({"data": [1, 2, 3]})
# Streaming load
buf.seek(0)
unpickler = psp.Unpickler(buf)
result = unpickler.load()
Security
pysafe-pickle never calls __reduce__, __setstate__, or any arbitrary code during deserialization. Only allowlisted types can be loaded.
# Restrict deserialization to specific types
psp.loads(data, allowlist={"builtins.dict", "builtins.list"})
Allowlisted types
By default, pysafe-pickle supports:
| Type | Notes |
|---|---|
None, bool, int, float |
Primitives |
str, bytes |
Strings and binary |
list, tuple |
Sequences |
dict |
Mappings |
set, frozenset |
Sets |
dataclasses |
Any @dataclass instance |
Any type not in this list raises UnsafeTypeError unless added to the allowlist.
Integrity verification
key = b"my-secret-key"
encoded = psp.dumps(data, hmac_key=key)
decoded = psp.loads(encoded, hmac_key=key) # raises HMACError if tampered
Migration from v1.0.x (pygraph)
In v1.0.x, the package was imported as import pygraph. In v1.1.0:
- The canonical import is now
import pysafe_pickle as psp. - Zero code breaks: Existing code using
import pygraphorfrom pygraph.migrations import migratecontinues working identically via a backward-compatible shim, emitting aFutureWarning. - Binary compatibility: Files serialized with v1.0.x (magic
PYGR) continue to deserialize seamlessly with zero warnings. New files are encoded with thePSPKmagic header. - The
pygraphshim will remain supported through v1.x and will be removed in v2.0.0.
# Legacy (deprecated in v1.1.0, emits warning, still works)
import pygraph
pygraph.dumps(data)
# Recommended
import pysafe_pickle as psp
psp.dumps(data)
Benchmarks
Run the benchmark suite to compare pysafe-pickle vs pickle:
uv run pytest benchmarks/ -v --benchmark-only
Development
# Install and build with uv / maturin
uv run maturin develop
# Run tests
cargo nextest run
uv run pytest tests/ -v
License
AGPL-3.0-only
Release files for pysafe-pickle 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pysafe_pickle-1.1.0-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details |
| pysafe_pickle-1.1.0-cp310-abi3-manylinux_2_34_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.34+ x86-64 | Details |
| pysafe_pickle-1.1.0-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 695.4 kB
Release files / pysafe_pickle-1.1.0-cp310-abi3-win_amd64.whl
| Download URL | pysafe_pickle-1.1.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 164.2 kB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
155577c78d36dbb24d9657b7628c45fdb7f675f17a43d097fc2de3164b0c5583
|
|
BLAKE2b-256 checksum How to use checksums |
9633391e406f7ba2d8c473c93cdf178f1719898e2a8ba089536a6afc2711b87c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency logRelease files / pysafe_pickle-1.1.0-cp310-abi3-manylinux_2_34_x86_64.whl
| Download URL | pysafe_pickle-1.1.0-cp310-abi3-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 276.9 kB |
| Tags | CPython 3.10 Linux glibc 2.34+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
aef190405952dbc6ade24c2f0fbaeba848fcf3bcdf16de2de771dc620e3c61a2
|
|
BLAKE2b-256 checksum How to use checksums |
6909c28a1f4526137b57eedf1b7f27c2cc2851fe60f22cf9d4b3f641588e2c72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency logRelease files / pysafe_pickle-1.1.0-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | pysafe_pickle-1.1.0-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 254.3 kB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
58bf96d1625738614588d1e551049d65a15dbfaa353e7c5c45c07c51e16c8736
|
|
BLAKE2b-256 checksum How to use checksums |
dde7536a1f450a515201f46f32973afd97b08883b4617a355959af112976ada9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency log