Skip to main content

SparQSim Banner

SparQSim / pysparq

English | 简体中文

arXiv:QRAM arXiv:SparQ PyPI License GitHub Docs

pysparq — a full-featured Python framework for sparse-state quantum circuit simulation (Register Level Programming, native QRAM, dynamic operators, RIR interpreter)

Highlights

  • Sparse-state quantum simulation with Register Level Programming — direct register-level arithmetic, native QRAM, dynamic operators, and an RIR interpreter (see the quick start below)
  • Quantum linear-system solving, dual engines — discrete-adiabatic QDA and Chebyshev-quantum-walk CKS solvers, validated end to end up to 2^20 dimensions on a single A800 GPU (v1d, v1e)
  • CPU (OpenMP) and CUDA backends with bitwise kernel cross-validation (v1c)

Repository Responsibilities

Dependency direction: SparQSim → QRAM-Simulator. SparQSim releases the pysparq package and hosts the SparQ C++ framework (SparQ/ sparse-state simulator + SparQ_Algorithm/ algorithm library + all Python bindings and algorithm-class experiments); the QRAM base (Common + QRAM + ThirdParty) is released independently from the QRAM-Simulator repository and is referenced and compiled by this repository as a git submodule (relative URL ../QRAM-Simulator.git).

Current core dependency

extern/qram-simulator is pinned to QRAM-Simulator main commit 8016d2014f57e17c7ee1dfd8d5200e7635feaec9. This replaces the former CUDA feature-branch pin with an integrated main-line core, preserving CUDA build support alongside the current exact joint damping/pruning implementation. Initialize the declared gitlink with git submodule update --init --recursive; do not substitute an arbitrary sibling checkout.

The gitlink is a fixed source commit, not a request to follow QRAM's latest branch tip. Dependency auditing fetches complete QRAM history before checking that the selected commit is on main. A shallow submodule clone can otherwise hide this ancestry when QRAM main advances, even though the locked source is still valid. Fetching history preserves the pin; it does not upgrade it or replace the required ancestry assertion.

The CUDA consumer CI verifies main-line ancestry and actually compiles all four device libraries (Common, QRAM, SparQ simulator and algorithm library) under pinned NVIDIA12.8.1 and13.3.0 SDKs. CPU wheels remain CPU-only. Compiling sm80 on a driver-free runner does not verify GPU execution or throughput. Local source-wheel regression passed486 tests; the pre-existing two CKS replacement-API skips and alpha=0 block-encoding xfail remain explicit gaps. Neither those skips nor the historical GPU reports certify the entire current software acceptance matrix.

Repository Contents PyPI package
SparQSim (this repository) SparQ C++ framework + the full-featured pysparq Python framework (rich core.cpp bindings + pure-Python algorithm layer) pysparq
QRAM-Simulator Pure C++ QRAM base (Common + QRAM circuit core + QRAM paper experiments + thin pybind11 bindings) qram-simulator

Installation

pip install pysparq

Requirements: Python 3.10 – 3.13, NumPy.

Standalone simulator workbench

pysparq info
pysparq run --case ghz --qubits 32 --out results/ghz.json
pysparq run --case qft --qubits 6 --basis 3
pysparq run --case stateprep --qubits 8 --seed 20261109
pysparq gui

The installed package contains its own local GUI and native CPU experiments; no separate demo-suite or external web assets are needed. GHZ keeps two nonzero amplitudes up to 32 qubits. Fourier and complex state preparation support 2..10 qubits in this bounded workbench; state preparation deliberately includes a zero first amplitude. Each run compares complex amplitudes against an independent reference and checks the actual inverse. JSON/CSV exports include amplitudes, logical qubits, sparse support, native binary hash and separate constructor/execution times. These are classical CPU simulation times, not quantum runtime estimates or application speedup certificates.

pysparq gui --no-browser --port 8000 prints a loopback URL. Its experiments run in separate subprocesses with a 60-second deadline because the native register system is process-global. Calling pysparq.demo.run directly clears that register system; use a separate process when sharing other simulator work.

If you need the QRAM circuit-level Python API (the QRAMCircuitQubit/QRAMCircuitQutrit noise-simulation workflow), additionally install the standalone package released by the QRAM-Simulator repository:

pip install qram-simulator

GPU support: the CUDA/GPU backend is disabled by default; enable it at build time by passing -DSPARQ_ENABLE_CUDA=ON (requires a local CUDA toolchain; verified with CUDA 13 / CCCL 3 and with CUDA 12.8 / sm_80 on an 8×A800 Linux server — see docs/verification/v1c-gpu-cuda-a800.md; the 2^20 CKS/QDA linear-solver production runs on this backend are recorded in v1e and v1d); the PyPI wheel is always CPU-only.

MPI: the SparQSim C++ core itself ships no MPI path; trajectory-level MPI ensemble parallelism for the qram-simulator bindings (single-node multi-process, results independent of the process count) is provided by the QRAM-Simulator repository as qram_simulator.mpi — see its "MPI Ensemble Parallelism" section.

Building from Source

git clone --recurse-submodules <this-repo-url>
cd SparQSim
pip install .

5-Minute Quick Start

import pysparq as ps

# 1. Create a sparse state
state = ps.SparseState()

# 2. Define registers (the core of Register Level Programming)
addr_id = ps.AddRegister("addr", ps.UnsignedInteger, 4)(state)
data_id = ps.AddRegister("data", ps.UnsignedInteger, 8)(state)

# 3. Initialize a superposition (all addresses with equal probability)
ps.Hadamard_Int("addr", 4)(state)

# 4. Create a QRAM and load data
memory = [i * 2 for i in range(16)]
qram = ps.QRAMCircuit_qutrit(addr_size=4, data_size=8, memory=memory)

# 5. Perform the QRAM load: |addr⟩|0⟩ → |addr⟩|memory[addr]⟩
ps.QRAMLoad(qram, "addr", "data")(state)

# 6. Do arithmetic directly (no gate compilation needed!)
ps.Add_ConstUInt_InPlace("data", 5)(state)   # data = data + 5

# 7. Measure / query probabilities
ps.set_seed(0)
outcome, prob = ps.MeasureZ("data")(state)
dist = ps.Probability.distribution(state, "addr")

Key Register-Level APIs

# Quantum arithmetic - direct register operations (core of Register Level Programming)
ps.Add_UInt_UInt(in1, in2, out)      # out = in1 + in2
ps.Add_UInt_ConstUInt(reg, const)    # reg = reg + const
ps.Mult_UInt_ConstUInt(in, c, out)   # out = in * c
ps.ShiftLeft(reg, n)                 # shift left by n bits
ps.ShiftRight(reg, n)                # shift right by n bits

# Basic quantum gates
ps.Hadamard_Int(reg, n_digits)       # apply Hadamard to an integer register
ps.X_Bool(reg, pos)                  # X gate (on a specific bit)
ps.Z_Bool(reg, pos)                  # Z gate

# QRAM operations
ps.QRAMLoad(qram, addr_reg, data_reg)      # QRAM load
ps.QRAMLoadFast(qram, addr_reg, data_reg)  # fast version

# Seedable measurement / reset / probability queries (for dynamic executors: mid-circuit MEASURE/RESET/QIF)
ps.set_seed(seed)                          # seed the global random engine, making sampling results reproducible
outcome, prob = ps.MeasureZ(reg)(state)    # projective Z-basis measurement: collapse + renormalization
measured = ps.Reset(reg, target=0)(state)  # measure + classically conditioned flips, forcing a reset to target
p = ps.Probability(reg, value)(state)      # read-only Born probability query, leaves the state unchanged
dist = ps.Probability.distribution(state, reg)  # full outcome distribution of a single register (read-only)

High-Level Algorithm Library (pysparq.algorithms)

An algorithm layer implemented in pure Python that composes public primitives (Grover, Shor, QDA, CKS, state preparation, block encoding, etc.); its one-to-one correspondence with the C++ experiment code is documented in docs/algorithm-implementation.md.

Quantum Linear-System Benches (CKS / QDA, validated at 2^20)

The C++ layer ships production Poiseuille tridiagonal linear-system benchmarks (A = tridiag(-1, α, -1), b = ones(n)/sqrt(n), κ = 16) with an identical CLI and artifact schema for both engines (residual_curve.csv + qda_summary_cpp.json):

# QDA (discrete adiabatic) — at 2^20 the default --czEps prunes the solution
# branch; 1e-16 is the canonical production setting (see the sizing guide below)
./Experiment_PoiseuilleQDABench_cuda --nqubit 20 --kappa 16 --steprate 1.1 \
    --tol 1e-6 --logEvery 250 --czEps 1e-16 --outdir qda_2p20

# CKS (Chebyshev quantum walk, QRAM-free direct oracles)
./Experiment_CKS_PoiseuilleBench_cuda --nqubit 20 --kappa 16 --eps 0.01 \
    --ds 32 --coef true --J 1024 --logEvery 64 --tol 1e-6 --outdir cks_2p20

Verified results (single A800, CUDA sparse-state backend):

  • CKS at 2^20 (QRAM-free direct oracles, built with -DCACHED_REGISTER_SIZE=16): direction residual 0 ≤ 1e-6 with early termination at 640/1024 Chebyshev terms, fidelity 1.0000000000, success probability 4.75e-2, 20,971,512 walk states, 2682 s wall time; dim16/dim64 success probabilities bitwise-identical to the CPU reference — v1e.
  • QDA at dim256: the full 40568-step schedule converges to res_dir = 5.9485e-4 (fidelity 1.000000, success probability 1.0).
  • QDA at 2^20 (three-run --czEps matrix, final): the canonical run (--czEps 1e-16) ends at res_dir = 5.178909e-3, fidelity 0.9999989, success probability 0.0017 (133,231 s); the 1e-20/1e-22 companions end at ~4.3e-2 with identical transfer. At this budget the adiabatic transfer is incomplete at 2^20 (success probability falls 1.0 → 0.027 → 0.0017 for dim256 → 2^16 → 2^20 on the same schedule) — a budget-vs-spectral-gap property of the algorithm, not a simulator defect; the ≥1e6-dimension convergence criterion is carried by CKS — v1d.

Sizing --czEps by dimension and schedule (QDA)

ClearZero prunes basis states with |amplitude|² < eps. The QDA solution branch is born with per-state amplitudes ≈ sqrt(2e-6/n), shrinking linearly as the schedule is refined (ds = 1/steps), so the rule of thumb is keep sqrt(czEps) below the solution-branch birth amplitude:

Schedule Working --czEps
coarse (--steprate 0.1) 1e-16
fine (--steprate 1.1, production) 1e-16 – 1e-22 (canonical 1e-16; 1e-20–1e-22 retain more small-amplitude states)

At the library default 1e-14 (amplitude cutoff 1e-7) the solution branch is pruned at birth from dim 2^19 upward — measured cliff: 2^17 (2.9e-7) and 2^18 (1.5e-7) survive, 2^19 (7.4e-8) and 2^20 (3.7e-8) are pruned, which surfaced as all-NaN extraction in the first 2^20 run. Commit 10a96aa made the threshold dimension-adaptive via --czEps (default behavior bitwise-unchanged); the full analysis lives in the v1d addendum.

Documentation

The full documentation site is hosted on GitHub Pages: https://iai-ustc-quantum.github.io/SparQSim/

Project Structure

SparQSim/
├── SparQ/                  # SparQ C++ sparse-state simulator (umbrella target SparQ defined in the root CMake)
├── SparQ_Algorithm/        # High-level algorithm C++ library (state preparation, block encoding, Hamiltonian simulation, QDA, etc.)
├── Experiments/            # Quantum algorithm C++ experiments (QDA/Grover/QFT/Shor/QCNN/CKS/GHZ, etc.)
├── test/                   # C++ tests (SparQ unit tests + full CommonTest; gated by SPARQ_BUILD_TESTS)
├── extern/qram-simulator/  # QRAM base submodule (Common + QRAM + ThirdParty; relative URL ../QRAM-Simulator.git)
├── PySparQ/
│   ├── core.cpp            # pybind11 rich bindings (_core module)
│   ├── pysparq/            # Python package (operators/ algorithms/ rir conformance dynamic_operator)
│   └── test/               # pytest suite
├── docs/                   # Sphinx documentation + algorithm porting guide
├── examples/               # C++ and Python examples (C++ part gated by SPARQ_BUILD_EXAMPLES)
└── pyproject.toml          # pysparq package (scikit-build-core + setuptools-scm)

Release Process

  1. Merge changes into main on Gitea (the primary development repository);
  2. When a new core version is needed, first wait for QRAM-Simulator to release the corresponding tag, then run git submodule update --remote (or check out that tag) and commit the pin;
  3. Sync to the GitHub upstream IAI-USTC-Quantum/SparQSim;
  4. Update CHANGELOG.md and tag vX.Y.Z (continuing the pysparq version series; next release v0.2.0);
  5. Push the tag or create a GitHub Release → the pypi-publish workflow automatically builds cp310–313 × (manylinux / win_amd64) wheels + sdist (the sdist embeds the core source and is self-contained) and publishes them to PyPI (Trusted Publishing / OIDC).

The frozen API dependencies of external consumers (qecc_lang, quantum_cfd QFVM) are listed in PySparQ/consumer_runtime_inventory.json and enforced by PySparQ/test/test_consumer_runtime_contract.py.

Papers and Citation

See the QRAM-Simulator repository README.

About Us

This project is developed by IAI-USTC Quantum (the Quantum Artificial Intelligence Team at the Institute of Artificial Intelligence, Hefei Comprehensive National Science Center).

License

Apache-2.0 License

Metadata

Release files for pysparq 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 pysparq 0.3.0
File Size Uploaded Provenance Actions
pysparq-0.3.0.tar.gz 2.9 MB With provenance Details for pysparq-0.3.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for pysparq 0.3.0
File Actions
pysparq-0.3.0-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for pysparq-0.3.0-cp313-cp313-win_amd64.whl
pysparq-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 pysparq-0.3.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
pysparq-0.3.0-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for pysparq-0.3.0-cp312-cp312-win_amd64.whl
pysparq-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 pysparq-0.3.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
pysparq-0.3.0-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for pysparq-0.3.0-cp311-cp311-win_amd64.whl
pysparq-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 pysparq-0.3.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
pysparq-0.3.0-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for pysparq-0.3.0-cp310-cp310-win_amd64.whl
pysparq-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 pysparq-0.3.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Total release size: 55.2 MB

Release files / pysparq-0.3.0.tar.gz

Download URL pysparq-0.3.0.tar.gz
Size 2.9 MB
Tags Source
SHA-256 checksum
How to use checksums
5c41e7679efd0f5c13d6f3b9c8afa9bdf86e715a5d8ddf05539041cad2855490
BLAKE2b-256 checksum
How to use checksums
fb61e9fb9478c604d0ee2f3bd822abae88e43f7928cd49039cec6257d2a72c78
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

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

Download URL pysparq-0.3.0-cp313-cp313-win_amd64.whl
Size 9.5 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
ae34a4ede342fb79b48df015f97a1224ff878433ffa25a7e43b99c470a41cf4a
BLAKE2b-256 checksum
How to use checksums
2e3f000717f809c20535ab992a1e9074cb711585fb15be0c1619cec3e3b0c8a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

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

Download URL pysparq-0.3.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 3.5 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
8a369abdfea178f1a4500e706432a3cb2787d395b304978cde09915adaaf575b
BLAKE2b-256 checksum
How to use checksums
b48870d368d5e8af3bdf377335563db5588c118a030d37888abce50c6488b0c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

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

Download URL pysparq-0.3.0-cp312-cp312-win_amd64.whl
Size 9.5 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
95541398cef2347d13bf9b4886a4c717ae860b90e210a26f1d63185c3d943358
BLAKE2b-256 checksum
How to use checksums
656060694665ec76d3cdc85098e0648f41afb48ce218ae659fd6b61fbafe028a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

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

Download URL pysparq-0.3.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 3.5 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
b710b7002b08a0ff8623b782eda2143966d9771c39bc1abaeb765e96e783141f
BLAKE2b-256 checksum
How to use checksums
e3d793872b8e78f194f2c5024c353cb991a1d9da07a2501c117295d6b5145b40
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

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

Download URL pysparq-0.3.0-cp311-cp311-win_amd64.whl
Size 9.5 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
6f26fbb4b2cedecf852f09bbe09ba4e95f6cc7d73f9e59bfe7aeabcf9f5ef28e
BLAKE2b-256 checksum
How to use checksums
fd84f78461ae9737e2f82026814a444c7a09e117e80dd921dbdfa48ec6c5709d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

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

Download URL pysparq-0.3.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 3.6 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
ffc406bc546936155873780d7ec570a0a958a0060f0980341a87c235e5905d55
BLAKE2b-256 checksum
How to use checksums
4fc7e187c0658497c081c4d0fa01aa66370e3dbe29a27efd4131b6d810cb0d40
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

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

Download URL pysparq-0.3.0-cp310-cp310-win_amd64.whl
Size 9.5 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
ac4e593d4a660210d09373a4e0af447e6058f40661a427aa3d23420d3c6f0f59
BLAKE2b-256 checksum
How to use checksums
438dcfec193fdaaab6eedbb8f57517adaec3166d2ef5b07dac14558ed4b1ea4f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

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

Download URL pysparq-0.3.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 3.6 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
ad3c0e988b7fc16e1d0b71ebc4f872e7eee5122cadb544dadf15a98e4f11576a
BLAKE2b-256 checksum
How to use checksums
d6742c916855b0ed895cf68b33a13b971e999c4bdf090ff072095f96d213aef4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

Security for pysparq 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 9 files in this release have been uploaded with provenance metadata.

Select from 9 files

Attestation for pysparq-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 Nov 9, 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