Skip to main content

rjson

PyPI CI License: MIT Python 3.10–3.14 Status: experimental

Fast JSON for Python, written in Rust directly against the CPython C API. A faster alternative to orjson and the standard library json for web APIs (FastAPI, Django, Flask), logging and NDJSON, caches and message queues; switching is mostly a find-and-replace (migration guide).

  • Faster than orjson on 18 of the 20 cases of the reference benchmark (geomean loads 1.17×, dumps 1.36×) and on 21 of 22 production-shaped workloads (1.52×); 3.5× / 14× faster than json.
  • Same output as orjson, byte for byte, including datetime, UUID, dataclasses and Enum; dumps_str returns a str directly.
  • Hardened for untrusted input: differential fuzzing against json, an AddressSanitizer CI build, and stack checks for deeply nested documents.
  • A JSON beautifier on the command line: rjson is a drop-in python -m json.tool (same output) that is 2–10× faster on real files, with in-place formatting and a CI --check (command line).
  • CPython 3.10–3.14 wheels for Linux (glibc and musl), macOS and Windows. MIT licensed.
Terminal: python benches/demo.py. rjson vs orjson with the same output: twitter.json loads 1.16x faster, twitter.json dumps 1.84x, github.json dumps 1.89x, 2k events with datetime and UUID 2.04x, twitter.json as str 1.77x.

If rjson saves you CPU time, a ⭐ on GitHub helps other people find it.

Geometric-mean speedups on CPython 3.13: loads 1.17× faster than orjson, dumps 1.36× faster than orjson, loads 3.53× and dumps 14.2× faster than the standard library json. Per-case speed relative to orjson. loads: 1.09× to 1.33× faster on nine cases, 0.95× on citm_catalog. dumps: 1.03× to 3.19× faster on nine cases, 0.93× on the float array.
Numbers behind the charts, and how they were measured

Speedup = other library's time ÷ rjson's time (higher is better). Median time per call over 5 runs, CPython 3.13.12, orjson 3.12.0, x86_64 (Xeon), PGO build (scripts/build_pgo.sh, as the published wheels are built). loads parses the documents' UTF-8 bytes; dumps returns bytes in both rjson and orjson. Raw results, with each case's per-run range: docs/img/benchmark-results.json.

case loads vs orjson dumps vs orjson loads vs json dumps vs json
twitter.json 1.20× 1.71× 3.23× 12.9×
citm_catalog.json 0.95× 1.12× 2.23× 6.06×
canada.json 1.09× 1.10× 4.34× 17.7×
github.json 1.33× 1.89× 2.98× 18.0×
small dict 1.27× 1.27× 6.37× 18.5×
records 1.12× 1.34× 2.17× 11.8×
unicode strings 1.12× 1.05× 1.80× 54.0×
escaped strings 1.22× 3.19× 5.14× 5.38×
int array 1.16× 1.03× 3.33× 11.1×
float array 1.26× 0.93× 7.53× 18.6×
geomean 1.17× 1.36× 3.53× 14.2×

The two cases below 1× are within this host's run-to-run noise (citm loads ranged 0.87–1.17×, float array dumps 0.88–1.16× over the 5 runs).

Reproduce and redraw:

benches/fetch_corpus.sh                                   # sha256-pinned corpora -> benches/data/
scripts/build_pgo.sh python3.13 && pip install target/wheels/*cp313*.whl   # or a plain build
python benches/corpus_benchmark.py --json --repeat 11 --output-json results.json
python benches/make_charts.py results.json                # -> docs/img/*.svg + this table

dumps_str (returns str) is faster than orjson's dumps on 6 of 10 cases (geomean 1.13×); it trails on twitter.json and unicode strings, because a str holding emoji must be stored at 4 bytes per character, and is at parity on citm_catalog and the float array (1.01, 1.05). loads of the same large non-ASCII str object over and over is 1.1–1.5× slower than orjson (twitter, citm, unicode strings): orjson keeps a UTF-8 copy attached to that string, which rjson deliberately does not (it would double the string's memory, #10); with bytes or a new str per call, as a server gets, rjson is faster. In plain (non-PGO) builds single cases move by up to 1.5× with code layout (canada dumps), which PGO removes. Methodology, per-version results and the roadmap: docs/PERFORMANCE_REVIEW.md.

On production-shaped workloads

Speed relative to orjson on 22 production-shaped workloads: rjson faster in 21, geomean 1.52×. Application types 1.09× to 3.17× (UTC datetimes), output as str 1.65× to 1.99×, web API 1.24× to 1.78×, escaped strings 1.40× and 1.56× with per-record NDJSON at 0.92×, standard corpora 1.09× to 1.82×.

Identical output is checked before timing. FastAPI, logging, NDJSON and Redis/Kafka numbers for the examples: Faster JSON in Python services. Numbers, method and the one slower case: docs/SHOWCASE.md (python benches/showcase.py).

Installation

The PyPI distribution is pyrjson (the name rjson on PyPI belongs to an unrelated project). You still import rjson.

pip install pyrjson        # or: uv add pyrjson

Wheels are PGO-optimized builds for CPython 3.10–3.14 on Linux (manylinux and musllinux, x86_64 and aarch64), macOS (arm64 and x86_64) and Windows (x86_64), with build provenance attestations (gh attestation verify <wheel> --repo TinDang97/rjson). Elsewhere pip builds from the sdist, which needs a Rust toolchain. The development version:

pip install "git+https://github.com/TinDang97/rjson"
# or, from a checkout:
pip install maturin && maturin develop --release

Usage

from datetime import datetime
from decimal import Decimal
from uuid import uuid4

import rjson

data = rjson.loads('{"name": "rjson", "tags": ["fast", "safe"], "stars": 1e3}')
payload = rjson.dumps(data)        # b'{"name":"rjson","tags":["fast","safe"],"stars":1000.0}'
text = rjson.dumps_str(data)       # the same JSON as a str

rjson.dumps({"at": datetime(2024, 5, 1, 9, 30), "id": uuid4()})  # datetime, UUID, dataclass, Enum: native
rjson.dumps({"price": Decimal("9.99")}, default=str)             # convert the rest with default=
name kind notes
loads(data, *, lenient=False) function → object data: str, bytes, bytearray or memoryview (any layout)
dumps(obj, *, default=None, passthrough=0, non_str_keys=False, indent=None, separators=None, sort_keys=False, ensure_ascii=False, allow_nan=False) function → bytes UTF-8 JSON, like orjson.dumps
dumps_str(...) function → str same options; like json.dumps(obj, ensure_ascii=False, separators=(",", ":"))
dumps_bytes(...) function → bytes alias of dumps, kept for compatibility
PASSTHROUGH_DATETIME, _UUID, _DATACLASS, _ENUM int flags for passthrough=, combine with |
JSONDecodeError exception json.JSONDecodeError itself (a ValueError)
JSONEncodeError exception subclass of both TypeError and ValueError, like orjson.JSONEncodeError
__version__ str package version

The wheel ships type stubs (py.typed), so mypy and pyright check calls to rjson.

  • lenient=True (loads): accepts everything json.loads accepts, with the same result: NaN/Infinity/-Infinity, a UTF-8 BOM on bytes and numbers overflowing to inf are parsed natively (no speed cost); lone surrogates ("\ud83d", sent by JavaScript clients that cut an emoji in half), UTF-16/UTF-32 bytes and nesting deeper than 1024 go through json.loads. The default stays strict, like orjson.
  • Types: dict (str keys), list, tuple, str, int (any size), float, bool, None, and their subclasses (IntEnum, str enums, OrderedDict, namedtuple, …).
  • Native types, byte-identical to orjson: datetime (RFC 3339: 2024-05-01T09:30:00, .ffffff only when non-zero, +HH:MM when aware), date, time, uuid.UUID (lowercase, hyphenated), dataclasses (as objects; _-prefixed names skipped, as in orjson) and Enum members (their value). Subclasses of datetime/date/time/UUID go to default=. Three orjson bugs are not copied: a tzinfo whose utcoffset() raises, or a deleted __slots__ field, raise the Python error (orjson crashes); utcoffset() returning None gives no offset, as in isoformat() (orjson writes +00:00); an offset whose seconds round up to a whole hour carries into the hour (orjson writes +00:60).
  • passthrough=: rjson.PASSTHROUGH_* flags send those kinds to default= (or make them raise) instead, e.g. to tag them for an exact round trip (examples/codec.py), like orjson's OPT_PASSTHROUGH_*.
  • non_str_keys=True: dict keys may be int (any size), float, bool, None (written exactly as json.dumps writes them: "1", "1e-07", "NaN", "true", "null"), Enum members (their value), and datetime/date/time/UUID (their native text, like orjson's OPT_NON_STR_KEYS). Other key types raise; default= is not called for keys. Like json and orjson, a coerced key can duplicate a str key ({1: …, "1": …} writes "1" twice). Off by default: a non-str key raises.
  • indent= / sort_keys=: indent=2 and sort_keys=True give exactly the bytes of orjson's OPT_INDENT_2 and OPT_SORT_KEYS (keys sorted by code point; dataclass fields keep their order); other widths (indent=4, indent=0) lay out like json.dumps(indent=n). Compact calls pay nothing for them; the options themselves are not yet as fast as orjson's (twitter.json: sort_keys 0.78×, indent=2 0.48×).
  • json.dumps options: indent also takes a str (indent="\t"), and separators=, ensure_ascii=True (non-ASCII and DEL as \uXXXX, surrogate pairs above U+FFFF) and allow_nan=True (NaN/Infinity/-Infinity) behave as in json.dumps, so any json.dumps call has an exact equivalent (numbers aside, see floats below 1e-4). Only the defaults differ: compact, non-ASCII kept, NaN raises. With ensure_ascii=True, dumps also writes lone surrogates (as \udXXX, like json).
  • default=: called with each value rjson cannot serialize; its return value is serialized in its place (and passed to default again if still unsupported), as in json.dumps and orjson. Exceptions it raises propagate unchanged. It is not called for NaN/Infinity or dict keys (see non_str_keys=), which still raise. Supported values never reach it, so native data runs at full speed.
  • Errors: loads raises JSONDecodeError with pos/lineno/colno matching json. dumps/dumps_str raise JSONEncodeError for unsupported types, non-str keys (unless non_str_keys=True), NaN/Infinity, and nesting deeper than 254 (which also catches circular references), so both except TypeError and except ValueError catch it. A lone surrogate raises UnicodeEncodeError in dumps; dumps_str passes it through.
  • Precision: floats round-trip exactly (shortest representation, e.g. 1e+16), and integers of any size are exact in both directions. loads accepts nesting up to 1024.

Command line: JSON beautifier

pip install pyrjson also installs rjson, a faster drop-in for python -m json.tool: the same options and byte-for-byte the same output (checked against json.tool on the whole benchmark corpus), plus a formatter mode for files and CI.

$ curl -s https://api.github.com/repos/TinDang97/rjson | rjson --sort-keys --no-ensure-ascii
$ rjson data.json pretty.json            # beautify (indent 4, like json.tool)
$ rjson --compact data.json min.json     # minify (also --minify)
$ rjson --tab / --indent 2 / --no-indent # other layouts
$ rjson --json-lines --compact < events.jsonl   # JSON Lines / NDJSON, streamed
$ rjson -i --indent 2 config/*.json      # reformat files in place (only changed ones)
$ rjson --check --indent 2 config/*.json # CI: exit 1 if a file is invalid or not formatted
$ rjson --validate *.json                # exit 1 if a file is not valid JSON

Syntax colors on a terminal (--color auto|always|never; honors NO_COLOR, FORCE_COLOR, PYTHON_COLORS), NaN/Infinity accepted like json.tool (--strict rejects them), errors as json.tool prints them (JSON Lines errors name the input line), atomic in-place writes that keep file permissions. Also python -m rjson and python -m rjson.tool, and rjson.tool.beautify(text, indent=4, ...) from Python.

End to end, process start included (CPython 3.13, median of 5; benches/cli_benchmark.py, results):

input python -m json.tool rjson speedup
github.json (55 KB) 36 ms 35 ms 1.0× (process start dominates)
twitter.json (0.6 MB) 85 ms 41 ms 2.1×
citm_catalog.json (1.7 MB) 150 ms 47 ms 3.2×
canada.json (2.2 MB, floats) 380 ms 69 ms 5.5×
60 MB file, pretty-print 4.5 s 0.92 s 4.9×
60 MB file, --compact 4.0 s 0.47 s 8.5×
200k JSON Lines, --compact 4.5 s 0.45 s 9.9×

The only output difference from json.tool: floats below 1e-4 are written in shortest form (1e-7; json writes 1e-07, the same value). json.tool --json-lines FILE fails on CPython 3.13+ ("I/O operation on closed file"); rjson --json-lines FILE works.

Migrating from json or orjson

Most code migrates with a find-and-replace:

you wrote with rjson
json.loads(s) / orjson.loads(s) rjson.loads(s)
orjson.dumps(obj) rjson.dumps(obj) (same bytes)
json.dumps(obj, separators=(",", ":"), ensure_ascii=False) rjson.dumps_str(obj)
json.dumps(obj).encode() rjson.dumps(obj)
except json.JSONDecodeError / orjson.JSONDecodeError except rjson.JSONDecodeError
except TypeError / orjson.JSONEncodeError around dumps except rjson.JSONEncodeError (TypeError keeps working)
json.dumps(obj, default=f) / orjson.dumps(obj, default=f) rjson.dumps(obj, default=f)
orjson.dumps(datetime/UUID/dataclass/Enum) the same bytes
json.dumps({1: "a", None: "b"}) / orjson.dumps(obj, option=OPT_NON_STR_KEYS) rjson.dumps(obj, non_str_keys=True) (key text as json writes it)
orjson.dumps(obj, option=OPT_INDENT_2 | OPT_SORT_KEYS) rjson.dumps(obj, indent=2, sort_keys=True) (same bytes)
json.dumps(obj, indent=4, sort_keys=True) rjson.dumps_str(obj, indent=4, sort_keys=True, ensure_ascii=True) (drop ensure_ascii to keep non-ASCII)
json.dumps(obj) (all defaults) rjson.dumps_str(obj, separators=(", ", ": "), ensure_ascii=True, allow_nan=True) (same text)
python -m json.tool rjson / python -m rjson (same options, same output; command line)
orjson.dumps(obj, option=OPT_PASSTHROUGH_DATETIME) rjson.dumps(obj, passthrough=rjson.PASSTHROUGH_DATETIME) (also _UUID, _DATACLASS, _ENUM)
json.dumps(obj, default=lambda o: o.isoformat()) for datetimes rjson.dumps(obj) (the same text, except UTC offsets with a seconds part, which are rounded to the minute)

What does not carry over yet, and how to handle it:

feature status workaround
NaN / Infinity by design dumps raises unless allow_nan=True (then NaN, as json; orjson writes null)
floats below 1e-4 by design 1e-7, same as orjson; json writes 1e-07 (same value, different bytes)

FastAPI

from fastapi import FastAPI
from fastapi.responses import JSONResponse
import rjson

class RJSONResponse(JSONResponse):
    def render(self, content) -> bytes:
        return rjson.dumps(content)

app = FastAPI()

@app.get("/items")
def items() -> RJSONResponse:
    return RJSONResponse([{"id": 1, "name": "widget"}])

Return RJSONResponse(...) directly for dicts and lists. Measured on whole requests through the app, against stock FastAPI's own fast path (a return type, serialized by Pydantic's dump_json): a 50-row page is 1.25–1.4× faster, 1.8–1.9× with UUID/datetime/Enum fields, and a 1,000-row export 3.0–3.2× faster; against an endpoint without a return type, 9–74× (numbers). Don't set it as default_response_class: endpoints that return Pydantic models already go through dump_json. examples/fastapi_app.py adds a fallback for Decimal, Pydantic models and dataclasses, and rjson-parsed request bodies.

Django and Flask

# Django: a JsonResponse rendered by rjson
from django.http import HttpResponse, JsonResponse
import rjson

class RJSONResponse(JsonResponse):
    def __init__(self, data, safe=True, **kwargs):
        if safe and not isinstance(data, dict):
            raise TypeError("set safe=False to serialize non-dict objects")
        kwargs.setdefault("content_type", "application/json")
        HttpResponse.__init__(self, content=rjson.dumps(data), **kwargs)

# Flask: every jsonify() / dict return goes through rjson
from flask.json.provider import JSONProvider

class RJSONProvider(JSONProvider):
    def dumps(self, obj, **kwargs):
        return rjson.dumps_str(obj)

    def loads(self, s, **kwargs):
        return rjson.loads(s)

app.json = RJSONProvider(app)

examples/django_json.py and examples/flask_json.py add a fallback for Decimal, sets and dataclasses, and a request-body parser that turns invalid JSON into a 400 with the error position.

Logging, NDJSON, Redis and Kafka

  • examples/json_logging.py: a logging.Formatter writing one JSON object per line (2.2–2.5 µs per record, 2.4–2.7× faster than the same formatter on json), plus NDJSON read/write (writing 12.5× faster, reading 2.5–2.8×).
  • examples/codec.py: a versioned bytes codec for Redis/Kafka with typed round trips, and value_serializer/value_deserializer callables. Round trips of JSON-native payloads are 4.1–4.6× faster than the same codec on json, and faster than pickle.
  • docs/ASYNC.md: aiohttp, httpx, asyncpg, redis.asyncio and aiokafka one-liners.

Production use

The full report, with every number and how it was measured: docs/PRODUCTION_READINESS.md. In short, rjson is ready for services whose payloads are JSON-native (dicts, lists, strings, numbers), and not yet a drop-in for code that relies on orjson's options.

FAQ

Is it faster than orjson in real services, not just benchmarks? On our production-shaped suite (benches/production_benchmark.py: REST pages, request bodies, NDJSON logs, 100 MB files, cache blobs) rjson is faster on most shapes (geomean dumps 0.67×, loads 0.83× of orjson's time, PGO wheels) and uses 30–37% less peak memory on large loads. The report lists the few shapes where it is not.

Is it safe? It checks the exact type of every value, reserves the worst-case output size before writing, and version-gates every CPython internal it uses, with self-tests at import. Untrusted input is bounded: nesting limits plus a thread-stack check (deep documents raise RecursionError instead of overflowing a small thread stack), and CPython's integer digit limit. CI runs the tests, differential fuzzing against json and thread/re-entrancy stress tests, also on an AddressSanitizer build. It is still 0.x: pin the version. Report vulnerabilities privately: SECURITY.md.

Does it work with asyncio / uvloop? Yes. Calls are synchronous and hold the GIL, so a large payload blocks the event loop, and asyncio.to_thread does not help. docs/ASYNC.md shows what to do instead.

Is it thread-safe? Yes, on regular (GIL) CPython builds, including calls re-entered from default= and threads switching mid-call (stress-tested). Threads do not parallelize JSON work. Free-threaded builds (3.13t/3.14t) and subinterpreters are not supported yet. In threads with small stacks (musl/Alpine's 128 KiB default, threading.stack_size), very deep documents raise RecursionError: about 975 nested arrays or 620 nested objects fit in 128 KiB, the full 1024 levels in 256 KiB.

Why does dumps return bytes? It is what you send over the network or write to a file, and it avoids a copy. Use dumps_str when you need a str.

Should I compress, or switch to msgpack / Arrow to go faster? Compress in the transport (HTTP middleware, Kafka compression.type), and only payloads of a few KB and up: compression costs as much CPU as serialization. Binary formats aren't faster when the result is Python dicts, because creating objects dominates. Arrow and Polars win when data stays columnar. Numbers: Transfer size.

Why is dumps_str sometimes slower than dumps? A str containing emoji must store every character in 4 bytes, and CJK text in 2, while UTF-8 bytes stay compact.

Why does my previously accepted request now fail with a 422? By default loads rejects a UTF-8 BOM, NaN/Infinity literals and escaped lone surrogates, like orjson does (the stdlib accepts them). Pass lenient=True to accept exactly what json.loads accepts.

Compatibility

  • CPython 3.10–3.14 on Linux x86_64/aarch64, macOS arm64 and Windows (CI). x86_64 builds target x86-64-v2 and select AVX2/AVX-512 kernels at runtime.
  • Not supported: PyPy, GraalPy, free-threaded (no-GIL) builds, subinterpreters.

Status

Experimental. The API may change before 1.0; pin the version you test against.

Why it is faster than orjson

Design differences from orjson 3.12. loads: orjson parses into a yyjson tree, then converts the tree to Python objects in a second pass; rjson builds Python objects in one pass (1.09–1.29× faster, 30–37% less peak memory on large files). dumps: orjson starts from a 4 KiB buffer that doubles, escapes with SSE2 or an AVX-512 build and returns bytes; rjson sizes the buffer from recent calls, escapes with AVX-512, AVX2 or SSE2 and writes bytes or str directly (1.12–1.82× faster, as str 1.65–1.99×). Native types: orjson probes three attributes and calls utcoffset() per aware datetime; rjson caches the timezone offset and per-class facts (UTC datetimes 3.17×, datetime/UUID/Enum records 2.34×, slots dataclasses 2.14×).

Both are Rust on the CPython C API, cache dict keys and format floats with zmij. Internals rjson relies on are version-gated and self-tested at import (CLAUDE.md); details in docs/PERFORMANCE_REVIEW.md.

Contributing

Bug reports and pull requests are welcome. CONTRIBUTING.md covers the development setup, the hard rules for code that touches the C API, and how to benchmark. Security issues: SECURITY.md. Changes: CHANGELOG.md.

uv venv .venv -p 3.13 && . .venv/bin/activate
uv pip install maturin orjson pytest
maturin develop --release && python -m pytest tests -q
path contents
src/parser.rs, src/lemire.rs loads
src/ser.rs dumps / dumps_str
src/entry.rs, src/compat.rs C-API entry points, version-portable helpers
tests/ pytest suites
python/rjson/ package: __init__.py, the command line (tool.py, __main__.py), type stubs (__init__.pyi)
examples/ FastAPI, Django, Flask, logging/NDJSON and Redis/Kafka integrations (tested)
benches/ corpus_benchmark.py (reference), showcase.py (vs orjson on production shapes), production_benchmark.py (production workloads), examples_benchmark.py (the examples on rjson vs json vs orjson), cli_benchmark.py (the command line vs json.tool), perf_gate.py, make_charts.py / make_showcase_charts.py / make_demo_svg.py (README charts, demo), demo.py
docs/ showcase, performance review, production readiness report, async guide
Troubleshooting source builds
  • Linker errors (symbol(s) not found for architecture arm64): Python and Rust must target the same architecture. Check with python3 -c "import platform; print(platform.machine())"; on Apple Silicon use an arm64 Python such as /opt/homebrew/bin/python3, then cargo clean and rebuild.
  • Missing Python headers: install your Python's development package (e.g. python3-dev).

Roadmap

  • Streaming decoder/encoder for async I/O; free-threading and subinterpreter support (docs/ASYNC.md)
  • Performance: NEON kernels for aarch64

License

MIT © 2025 Tin Dang. src/lemire.rs is adapted from fast-float (MIT OR Apache-2.0).

Metadata

Release files for pyrjson 0.3.0

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

Source distribution (sdist)

Source distribution for pyrjson 0.3.0
File Size Uploaded Provenance Actions
pyrjson-0.3.0.tar.gz 397.1 kB With provenance Details for pyrjson-0.3.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for pyrjson 0.3.0
File Actions
pyrjson-0.3.0-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for pyrjson-0.3.0-cp314-cp314-win_amd64.whl
pyrjson-0.3.0-cp314-cp314-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ x86-64 Details for pyrjson-0.3.0-cp314-cp314-musllinux_1_2_x86_64.whl
pyrjson-0.3.0-cp314-cp314-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ ARM64 Details for pyrjson-0.3.0-cp314-cp314-musllinux_1_2_aarch64.whl
pyrjson-0.3.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64 Details for pyrjson-0.3.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
pyrjson-0.3.0-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ ARM64 Details for pyrjson-0.3.0-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
pyrjson-0.3.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for pyrjson-0.3.0-cp314-cp314-macosx_11_0_arm64.whl
pyrjson-0.3.0-cp314-cp314-macosx_10_12_x86_64.whl CPython 3.14 CPython 3.14 macOS 10.12+ x86-64 Details for pyrjson-0.3.0-cp314-cp314-macosx_10_12_x86_64.whl
pyrjson-0.3.0-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for pyrjson-0.3.0-cp313-cp313-win_amd64.whl
pyrjson-0.3.0-cp313-cp313-musllinux_1_2_x86_64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ x86-64 Details for pyrjson-0.3.0-cp313-cp313-musllinux_1_2_x86_64.whl
pyrjson-0.3.0-cp313-cp313-musllinux_1_2_aarch64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ ARM64 Details for pyrjson-0.3.0-cp313-cp313-musllinux_1_2_aarch64.whl
pyrjson-0.3.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details for pyrjson-0.3.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
pyrjson-0.3.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ ARM64 Details for pyrjson-0.3.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
pyrjson-0.3.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for pyrjson-0.3.0-cp313-cp313-macosx_11_0_arm64.whl
pyrjson-0.3.0-cp313-cp313-macosx_10_12_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.12+ x86-64 Details for pyrjson-0.3.0-cp313-cp313-macosx_10_12_x86_64.whl
pyrjson-0.3.0-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for pyrjson-0.3.0-cp312-cp312-win_amd64.whl
pyrjson-0.3.0-cp312-cp312-musllinux_1_2_x86_64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ x86-64 Details for pyrjson-0.3.0-cp312-cp312-musllinux_1_2_x86_64.whl
pyrjson-0.3.0-cp312-cp312-musllinux_1_2_aarch64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ ARM64 Details for pyrjson-0.3.0-cp312-cp312-musllinux_1_2_aarch64.whl
pyrjson-0.3.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details for pyrjson-0.3.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
pyrjson-0.3.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ ARM64 Details for pyrjson-0.3.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
pyrjson-0.3.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for pyrjson-0.3.0-cp312-cp312-macosx_11_0_arm64.whl
pyrjson-0.3.0-cp312-cp312-macosx_10_12_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.12+ x86-64 Details for pyrjson-0.3.0-cp312-cp312-macosx_10_12_x86_64.whl
pyrjson-0.3.0-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for pyrjson-0.3.0-cp311-cp311-win_amd64.whl
pyrjson-0.3.0-cp311-cp311-musllinux_1_2_x86_64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ x86-64 Details for pyrjson-0.3.0-cp311-cp311-musllinux_1_2_x86_64.whl
pyrjson-0.3.0-cp311-cp311-musllinux_1_2_aarch64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ ARM64 Details for pyrjson-0.3.0-cp311-cp311-musllinux_1_2_aarch64.whl
pyrjson-0.3.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64 Details for pyrjson-0.3.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
pyrjson-0.3.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64 Details for pyrjson-0.3.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
pyrjson-0.3.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for pyrjson-0.3.0-cp311-cp311-macosx_11_0_arm64.whl
pyrjson-0.3.0-cp311-cp311-macosx_10_12_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.12+ x86-64 Details for pyrjson-0.3.0-cp311-cp311-macosx_10_12_x86_64.whl
pyrjson-0.3.0-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for pyrjson-0.3.0-cp310-cp310-win_amd64.whl
pyrjson-0.3.0-cp310-cp310-musllinux_1_2_x86_64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ x86-64 Details for pyrjson-0.3.0-cp310-cp310-musllinux_1_2_x86_64.whl
pyrjson-0.3.0-cp310-cp310-musllinux_1_2_aarch64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ ARM64 Details for pyrjson-0.3.0-cp310-cp310-musllinux_1_2_aarch64.whl
pyrjson-0.3.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ x86-64 Details for pyrjson-0.3.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
pyrjson-0.3.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ ARM64 Details for pyrjson-0.3.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
pyrjson-0.3.0-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for pyrjson-0.3.0-cp310-cp310-macosx_11_0_arm64.whl
pyrjson-0.3.0-cp310-cp310-macosx_10_12_x86_64.whl CPython 3.10 CPython 3.10 macOS 10.12+ x86-64 Details for pyrjson-0.3.0-cp310-cp310-macosx_10_12_x86_64.whl

Total release size: 13.0 MB

Release files / pyrjson-0.3.0.tar.gz

Download URL pyrjson-0.3.0.tar.gz
Size 397.1 kB
Tags Source
SHA-256 checksum
How to use checksums
03354bb667245c4f55711af8950ae74b5e39265980a62fa1f44cd1d19799ff15
BLAKE2b-256 checksum
How to use checksums
a5764dc6c6556677fd3bc71187f6d448aa0368d9a15ff7727dac906085a801e3
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp314-cp314-win_amd64.whl

Download URL pyrjson-0.3.0-cp314-cp314-win_amd64.whl
Size 297.1 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
a43aec18473be7abf229a3177e7c792d717f3b18d4fb78a2ed45d8e6077f445c
BLAKE2b-256 checksum
How to use checksums
d84dd33801bcb24bbdd5f1a7629fe2bbd310c839e4ae0df2e2e1f1295dd7bd86
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp314-cp314-musllinux_1_2_x86_64.whl

Download URL pyrjson-0.3.0-cp314-cp314-musllinux_1_2_x86_64.whl
Size 459.0 kB
Tags CPython 3.14 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
ab123a4c5b3a833998dd32b3d70306749e2188c67f0d5fff748bf0c32e80c41e
BLAKE2b-256 checksum
How to use checksums
339d3b9d4b178db7d9e84d06e26dff93cb55593e0683fd28c261424d40611c75
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp314-cp314-musllinux_1_2_aarch64.whl

Download URL pyrjson-0.3.0-cp314-cp314-musllinux_1_2_aarch64.whl
Size 399.2 kB
Tags CPython 3.14 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
660208e1ce12004179232564c964f7ead162464a5d9de777c2e4bf8ffc32e7ba
BLAKE2b-256 checksum
How to use checksums
ba4a069c665e3231c3695957abb26d1d7025bb5becc445f342a204fc23fb6fb4
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL pyrjson-0.3.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 359.5 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
09290cff6797893fffea052c401d208edf164fc1770c9ea637681b5b392ca0a6
BLAKE2b-256 checksum
How to use checksums
c1864c8e628ff00768bd261f0651d2b5a11a129295b7b9c6bc4aaa5d59fa1d51
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL pyrjson-0.3.0-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 320.0 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
5f6fa120af8347f9ae05bb04cc5a23be5a83f296c8a125479461b095d5bc2c95
BLAKE2b-256 checksum
How to use checksums
c56446e9c3e82c941aed3e2bcd4e69401a0b889219a528357097e4001bdc2694
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL pyrjson-0.3.0-cp314-cp314-macosx_11_0_arm64.whl
Size 316.3 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
563bc5b9a036ec45e3aa7d52918af7ecbc56e9a88cf7409dc142effdaaa6a1d2
BLAKE2b-256 checksum
How to use checksums
2771f5a3b6dd4d137c5b1e7c51b09b7bc30ddcc47f1f6b8b8ec68fccddc52110
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp314-cp314-macosx_10_12_x86_64.whl

Download URL pyrjson-0.3.0-cp314-cp314-macosx_10_12_x86_64.whl
Size 363.3 kB
Tags CPython 3.14 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
20d0baea11863c05eadc7319b460877fad110426bf1ebd7af21560d3d2da24a5
BLAKE2b-256 checksum
How to use checksums
575d3235ea4156f70c9c703b6cd3084eb3354a081df31864aba86a6473a97adc
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp313-cp313-win_amd64.whl

Download URL pyrjson-0.3.0-cp313-cp313-win_amd64.whl
Size 292.4 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
510c3b9b13a134943cf45113ad5f0ac174f5bb4cb846141b5eaa71144efe4a17
BLAKE2b-256 checksum
How to use checksums
090ff246c4bb6b882caa38bc5c829b8e1df606e063f3fe5ee160f0d13a0f5b60
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL pyrjson-0.3.0-cp313-cp313-musllinux_1_2_x86_64.whl
Size 461.3 kB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
77bc3d1f15f997d655181c11b98d3787f6d5e0c15cc6c9f1b746eeedd641a1ff
BLAKE2b-256 checksum
How to use checksums
c2c677a9ac7c341d534040a18d05cc7669ef9f12b56162164e6464713a59f253
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp313-cp313-musllinux_1_2_aarch64.whl

Download URL pyrjson-0.3.0-cp313-cp313-musllinux_1_2_aarch64.whl
Size 399.3 kB
Tags CPython 3.13 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
b8f2980572c09e7da488051785c5797afc7ef60aa050be4ff73113e522c4beab
BLAKE2b-256 checksum
How to use checksums
c98796e2492c6a8e51921fbdce6979d3b0614fe7dec3e8db43509babb820c909
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL pyrjson-0.3.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 363.2 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
3c8fc33ff0fb5894deb4eca946e5cc93fc61eacb6f1da50102a9d7dfc9b2286f
BLAKE2b-256 checksum
How to use checksums
639fbf8ed313b52be83d52e44b5bedc0e5bb5eeaaa779f93fdd6e3c4e19c3ae3
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL pyrjson-0.3.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 322.7 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
e72d75d5ebdca441cdb273bf4e72a3609ced9db9086a0244948760e3fdd45fdc
BLAKE2b-256 checksum
How to use checksums
c11a99338916e4753d67f4bd246557e6089bac2073d6c4e30ce1aca551308832
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL pyrjson-0.3.0-cp313-cp313-macosx_11_0_arm64.whl
Size 316.1 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
0d44fd7a70679eb64aa80c914ddbbd276aff621d451da4a73c4d7ce2f683d85c
BLAKE2b-256 checksum
How to use checksums
ccfd2462b31c48cc0e343a8fd81dd154a7574f454d99466bb85514329271c0b8
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp313-cp313-macosx_10_12_x86_64.whl

Download URL pyrjson-0.3.0-cp313-cp313-macosx_10_12_x86_64.whl
Size 361.3 kB
Tags CPython 3.13 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
7c8888238272d6e5b3ff83d6617db8fc8666ce03c6e77a433d258bc1ba189334
BLAKE2b-256 checksum
How to use checksums
9108deacffef49289fc191b81dcb6fa3ae137f1225d9073111b9079396b155f5
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp312-cp312-win_amd64.whl

Download URL pyrjson-0.3.0-cp312-cp312-win_amd64.whl
Size 292.5 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
b4e25cca9fb71fdb030a91fec14d1d9e515925fa3b09f4723df6a8694046bb77
BLAKE2b-256 checksum
How to use checksums
4f916395d6c487a6550ec2aa3d6708b9d0774e95aa8f74a8f12d9019190e0ad9
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL pyrjson-0.3.0-cp312-cp312-musllinux_1_2_x86_64.whl
Size 461.3 kB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
ce42d34a768e49fb58031424d25dad6a6147bb3c33508389c0eaabdd62d68cfe
BLAKE2b-256 checksum
How to use checksums
fcdc3ceb6b5265ce00322c9f2277b708c42a6fbba4247ca0c6298f8506773a5b
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp312-cp312-musllinux_1_2_aarch64.whl

Download URL pyrjson-0.3.0-cp312-cp312-musllinux_1_2_aarch64.whl
Size 399.0 kB
Tags CPython 3.12 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
8f88a5b02cf089e03a365eb1bdd0fde3be963dec48369cda1c2715785162bb8f
BLAKE2b-256 checksum
How to use checksums
083702d1ed3deb8b21800b9c60891e3703c67e59a6b72684b2bb69289f355fe2
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL pyrjson-0.3.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 363.8 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
d96c69c126a3379e3725a06f41ce4bf12bc7477a575c12d3722084c3842d9e5a
BLAKE2b-256 checksum
How to use checksums
a7072f358ddf6d6d59add025acded546bcc2ae1b0b7282728f178ab33a534e47
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL pyrjson-0.3.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 323.1 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
28e372a87cc1928b49623802394a0caeb8db9f17eac4512be1cc70e0c5b5a6e3
BLAKE2b-256 checksum
How to use checksums
4ea13ce942dea39d78ce2a243aa1a85a4a649cfb65d2ed13a4c06247944dabde
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL pyrjson-0.3.0-cp312-cp312-macosx_11_0_arm64.whl
Size 316.3 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
a6b0f7af5cdd2c780b6b42e01a9d975ecbab175a6fc7acba5596c3a79a4fcdb8
BLAKE2b-256 checksum
How to use checksums
4d285213b6a8ddbf50e15c0085c30a538ae3b0a51aef7b93e0553fd7646e7128
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp312-cp312-macosx_10_12_x86_64.whl

Download URL pyrjson-0.3.0-cp312-cp312-macosx_10_12_x86_64.whl
Size 368.8 kB
Tags CPython 3.12 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
a530c1cb0b1f4d9d9ef7cc30005d81d9f56e2f8ff3bd2d1c7c17b6bff4379135
BLAKE2b-256 checksum
How to use checksums
290b1ba16b07712584c2f113abdec35cc72670f5405b44936dc53aeac5ce70d9
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp311-cp311-win_amd64.whl

Download URL pyrjson-0.3.0-cp311-cp311-win_amd64.whl
Size 292.4 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
ce30a6a2fb6a2e06f1f4607a46e6b35ccd953cd8de0b302fc8ea0e776ad3998e
BLAKE2b-256 checksum
How to use checksums
b59a652de0cb25b2d0dac5124ac8a81bbcf28448e17aeb8f71d9f1bc5fd2e0fc
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL pyrjson-0.3.0-cp311-cp311-musllinux_1_2_x86_64.whl
Size 462.1 kB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
99e25435736018370b2235f66955133047adf35f4b0db1d02566da3589232c1f
BLAKE2b-256 checksum
How to use checksums
aaa739d44eb1570554f1d49989c72472ffaad60c765416a0e70adb31255ab7fb
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp311-cp311-musllinux_1_2_aarch64.whl

Download URL pyrjson-0.3.0-cp311-cp311-musllinux_1_2_aarch64.whl
Size 398.8 kB
Tags CPython 3.11 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
8663537ae550f66bb3b891992d2fc0333747f2352eca8ddfd5e742f1b5c20350
BLAKE2b-256 checksum
How to use checksums
c8cf619bd59e394002203d0a099941c9d42a9db8e51c798c8f6ef43f7d7d50e3
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL pyrjson-0.3.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 359.9 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
75709d35ccb041ea0dbcd58542f367f7c31d60d4fe4d26c7cd25f4d40e4d6ed3
BLAKE2b-256 checksum
How to use checksums
0ce38c7c35325b1610cc453592576e51d2207e49a6a5279bf19cb6e2560dc0fe
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL pyrjson-0.3.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 321.7 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
55e2d2e155dbbcc5f2dc06851eb47a7a2b9085d622071c07db5ad0b5ba19db76
BLAKE2b-256 checksum
How to use checksums
be9c770f7fc4d5eefa5227f86251656a65168033ea522047af8e9593600ae416
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL pyrjson-0.3.0-cp311-cp311-macosx_11_0_arm64.whl
Size 317.2 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
771ef08e6ce324b3e4c6384482dff54220cf5eb8f0363c07b7641f7c544526eb
BLAKE2b-256 checksum
How to use checksums
5cbb4c0d17b1a31736a5ff20af26bd7aac98586dc3543bc2a37748086dfb33a5
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp311-cp311-macosx_10_12_x86_64.whl

Download URL pyrjson-0.3.0-cp311-cp311-macosx_10_12_x86_64.whl
Size 374.0 kB
Tags CPython 3.11 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
31072e1a83be45217b8ab6713634d0edbce1038c7d8b43c8ca7d2f8b0335aa9a
BLAKE2b-256 checksum
How to use checksums
ead11045f6d8c0926ebfe5799a30e49d8de9a195e40751ff7fb9757be64afa79
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp310-cp310-win_amd64.whl

Download URL pyrjson-0.3.0-cp310-cp310-win_amd64.whl
Size 278.2 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
b15fa8c2b9897b3f5652a6f776152b796bb31650c06b5f4290aa3e0137c81fde
BLAKE2b-256 checksum
How to use checksums
5a76fc6eac2fa9049823a2d8fb216ebf6834b7487b530f4f93d9ec30300ade66
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp310-cp310-musllinux_1_2_x86_64.whl

Download URL pyrjson-0.3.0-cp310-cp310-musllinux_1_2_x86_64.whl
Size 456.4 kB
Tags CPython 3.10 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
f39057023b943c6ea74eba2e766720e8f46a97450b95eeefcac5a9b7be838bde
BLAKE2b-256 checksum
How to use checksums
319ef2c304eae8e9ff381506a657f45ee17e707e40d2fb80ecccc643888e870f
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp310-cp310-musllinux_1_2_aarch64.whl

Download URL pyrjson-0.3.0-cp310-cp310-musllinux_1_2_aarch64.whl
Size 387.4 kB
Tags CPython 3.10 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
6109db9e2971dfe021e0d73196809b78549c001fe8a25181a6abd9a339bee7bd
BLAKE2b-256 checksum
How to use checksums
975c4b24a0ac352a6b7c5d4d32199f6ffc18f82d8a1482236a1f9f3e3f19593a
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL pyrjson-0.3.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 353.9 kB
Tags CPython 3.10 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
e792206bd58b2ae6dc9f931a67fee53a42f92c063ff6bfb661d2a4458899edc5
BLAKE2b-256 checksum
How to use checksums
ef69f95758ff4cc0798315c8ad1844362f1c242e326965a8c9683067d194003f
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL pyrjson-0.3.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 317.7 kB
Tags CPython 3.10 Linux glibc 2.17+ ARM64
SHA-256 checksum
How to use checksums
f0b9490e03d4388bbaa554544fa35bb1cdfb5c579255a5f20bb0eee3a4fddb4b
BLAKE2b-256 checksum
How to use checksums
813b4f50b62d7752a89e006de52b5ce4ce3bde6f63b74223b4270d6537076f17
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp310-cp310-macosx_11_0_arm64.whl

Download URL pyrjson-0.3.0-cp310-cp310-macosx_11_0_arm64.whl
Size 312.9 kB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
69d5501b437995245a371a2a865e81ae1780c27f9911722582d689875ed54fe4
BLAKE2b-256 checksum
How to use checksums
6cece1027c03ca86afa838d6825654873a47419998c36bf89d342a07790b7392
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 28, 2026.

Transparency log

Release files / pyrjson-0.3.0-cp310-cp310-macosx_10_12_x86_64.whl

Download URL pyrjson-0.3.0-cp310-cp310-macosx_10_12_x86_64.whl
Size 367.0 kB
Tags CPython 3.10 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
4c701b3074c6616c3ddca91e4eacd5179852d677a0be82466b5cf991ec284483
BLAKE2b-256 checksum
How to use checksums
b544ee07ef90fa1e8c4419fdc19c4f4401349b92b35fe9f60f68f9af46996e4f
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 28, 2026.

Transparency log

Security for pyrjson 0.3.0

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

Select from 36 files

Attestation for pyrjson-0.3.0.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 Sep 28, 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.

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