Skip to main content

SymQ

Exact verification of reversible Boolean circuits, with opt-in, explicitly scoped quantum research extensions.

CI Python 3.11+ MIT license

SymQ computes exact algebraic normal forms (ANFs) of X/CX/CCX/MCX reversible circuits and decides their equivalence. It has pure-Python and optional native C/ZDD backends and a separate SAT engine. It also offers opt-in checkers for restricted measurement-assisted quantum programs. Each checker proves one named theorem. SymQ never switches silently between computing output functions, deciding classical equivalence and comparing quantum channels.

Status: experimental research software. The first release is 0.2.0; from it on, the classical core is kept compatible as the stability policy states, and the experimental and research layers carry no promise. SymQ is not a universal quantum-circuit verifier and not a formally verified implementation. Its verification paths do not export independently checkable certificates, except one opt-in research path for a narrow class of phase obligations (proof levels).

Navigate: Quick start · Question → theorem → API · Contextual substitution · Experimental APIs · Proof levels and replay · Installation · Limits · References

Quick start

This example needs only the pure-Python core: no SAT solver and no C compiler.

from symq import Budget, Circuit, check_equivalence

reference = Circuit(3)
candidate = Circuit(3).ccx(0, 1, 2).ccx(0, 1, 2)   # two Toffolis cancel
result = check_equivalence(reference, candidate, backend="sparse", budget=Budget(max_seconds=5))
assert result.equivalent

mutant = Circuit(3).ccx(0, 1, 2)                     # a real difference has a replayable input
different = check_equivalence(reference, mutant, backend="sparse")
assert not different.equivalent
assert reference.run(different.witness) != mutant.run(different.witness)

Wire indices start at zero, and controls come before the target (ccx(c1, c2, target)). Integer inputs are read least-significant bit first. From the command line, symq check left.qasm right.qasm decides the same question and symq anf circuit.qasm prints the exact output polynomials. Importers accept only strict subsets: symq.qasm.parse_qasm takes reversible OpenQASM 2/3 and rejects measurements and classical control; symq.kickmix.load_kmx takes Qualtran kickmix text, including HMR programs.

Question → theorem → API → limits

Start from the statement you want proved, not from the fastest-looking backend.

Question Theorem proved on success Entry point Main limits
What are the exact output functions? Exact ANF of every output wire make_algebra + simulate + to_anf ANF size can be exponential; backend width caps (backends)
Are two complete reversible circuits equal? Every output agrees on every Boolean input; a difference carries a replayed witness check_equivalence, symq check Classical permutations only
Are selected outputs equal under constants, restored wires or input assumptions? SAT/UNSAT of that declared classical contract symq.sat.Contract + check_sat_equivalence Budget may end inconclusive; no ANFs, no exported UNSAT certificate
Is a replacement valid at one site of a larger circuit? Contextual classical substitution: domain, prefix, interface and suffix obligations symq.labs.contextual_substitution.check_substitution, symq rewrite Sufficient, not complete; says nothing about quantum behaviour
Is a ±1-phase/HMR program a clean, outcome-independent rewrite? Strict branch equality under O1/O2 symq.phase.check_phase_equivalence Restricted grammar; O1/O2 must hold
Do two restricted HMR programs implement the same full or reduced channel? Equality on all coherent input pairs under an explicit physical frame symq.experimental.verify + VerificationContract Two Boolean variables per data bit; width caps
Do recorded measurement outcomes also agree? Equality of the observed instrument Experimental instrument theorem, hybrid-exact Bounded oracle; small programs
Does a reversible loader XOR an exact lookup table into its targets? For every legal address and target, on the coherent span: output = input ⊕ T[address] symq.experimental.check_table_xor X/CX/CCX/MCX only; ≤ 16 address and target bits

The first four rows are statements about classical Boolean functions. The table-XOR contract proves a basis permutation, which extends to the coherent span because the accepted gates have no phases. The three HMR rows have quantum semantics and are not interchangeable with classical equivalence. Channel equality does not imply equal measurement records, and equality after tracing does not imply full-output equality.

symq.verify(left, right, theorem=..., engine=...) routes each theorem to its owning engine. It never chooses a theorem or an engine for you. The result has outcome, reason, witness and certified. equivalent and different are true only for a proved equivalence or difference; both are false for inconclusive and unsupported.

A classical SAT contract

from symq import Budget, Circuit
from symq.sat import Contract, check_sat_equivalence

left = Circuit(3).ccx(0, 1, 2).ccx(0, 1, 2)
right = Circuit(3)
contract = Contract(observed_outputs=(0, 1), restored_wires=(2,))
verdict = check_sat_equivalence(left, right, contract, budget=Budget(max_seconds=10))
assert verdict.outcome == "equivalent"

A restored wire must return to its own original value, even when it is borrowed or dirty. An ignored wire is not implicitly restored.

Contextual substitution

A contextual rewrite replaces the gates in [start, stop) and asks whether the replacement is valid at that site. The prefix may establish facts, such as a clean scratch wire, that make the replacement valid there but not elsewhere.

from symq import Circuit
from symq.labs.contextual_substitution import SubstitutionContract, check_substitution
from symq.labs.rewrite import Weights

# Given the declared input q2 = 0, the first two gates leave q2 clean,
# so CX(q2, q0) at position 2 is the identity there.
source = Circuit(3).cx(0, 2).cx(0, 2).cx(2, 0).cx(0, 1)
contract = SubstitutionContract(initial_constants=((2, 0),), clean_at_cut=(2,))
result = check_substitution(source, (2, 3), Circuit(3), contract=contract,
                            weights=Weights.from_mapping({"cx": 3}))
assert result.equivalent and result.cost.weighted_delta == -3

# Without the declared input, the clean cut cannot be established: refused, never trusted.
refused = check_substitution(source, (2, 3), Circuit(3),
                             contract=SubstitutionContract(clean_at_cut=(2,)))
assert refused.outcome == "precondition_failed" and refused.candidate is None

From the command line, the same work is a four-step workflow, run here from a checkout with the provided examples:

symq locate examples/locate/source.json examples/locate/reference.json --theorem classical
symq prepare-rewrite examples/prepare/source.json examples/prepare/original.json \
  examples/prepare/candidate.json --contract examples/prepare/contract.json \
  --weights examples/prepare/weights.json --output-dir prepared
symq rewrite prepared/request.json --report prepared/proof.json
symq replay prepared/proof.json
  1. locate finds the unique exact occurrence of a small block and its wire map. It proves nothing.
  2. prepare-rewrite turns a small original/replacement pair into a full-width request in a new directory. It is strictly preparatory: its output says ready_for_proof, proved=false, candidate_authorized=false. It never replaces an existing path, and preparation.json is an advisory record of the emitted file hashes.
  3. rewrite proves (or refuses) the substitution and writes a report.
  4. replay recomputes the proof from the embedded request and refuses an edited report.

The cut predicate contains only what the contract declares. The theorem is therefore sufficient but not complete: a valid rewrite can be not_proved when its justification was not declared. A rewrite checker never reports a proved difference, because a local counterexample need not be reachable from the global input. These checkers live in symq.labs, which carries no API promise. See the rewrite guide.

Experimental APIs

SymQ has three installed layers and one development-only layer. None of them silently replaces another.

Layer Contents Promise
symq Circuits, algebras, classical equivalence, SAT contracts, verify facade, CLI Kept compatible as the stability policy states, from the first release; changes are recorded in the changelog
symq.experimental Restricted HMR channels and instruments, coherent domains, prepared references, serialization Installed, opt-in; explicit theorem, frame and backend required. No API promise
symq.labs Contextual rewrites and their preparation, phase certificates, the LRAT proof path, research prototypes (index) No API promise; may change or disappear
formal/ Lean 4 projects checked in development CI (formal runtime model, LRAT gate lemmas) Not installed, never imported by SymQ; Lean is not a runtime dependency

A restricted HMR channel check:

from symq.experimental import VerificationContract, verify
from symq.phase import PhaseProgram
from symq.resources import Budget

reference = PhaseProgram(2, 1)
candidate = PhaseProgram(2, 1).ccx(0, 1, 2)
event = candidate.hmr(2)
candidate.cz_if(event, 0, 1)
contract = VerificationContract(theorem="full_channel", backend="zdd")
assert verify(reference, candidate, contract, budget=Budget(max_seconds=10)).equivalent

A table-XOR loader check, from the opt-in experimental API:

from symq import Circuit
from symq.experimental import TableXorContract, check_table_xor

loader = Circuit(6).cx(0, 2).cx(1, 2).cx(1, 3)
contract = TableXorContract(
    width=6, address_wires=(0, 1), target_wires=(2, 3), clean_wires=(4,),
    borrowed_wires=(5,), table=(0, 1, 3, 2), legal_addresses=(0, 1, 2),
    target_values=None, table_id="t0", slot_id="s1", theorem="coherent",
)
assert check_table_xor(loader, contract, backend="exhaustive").equivalent
faulty = check_table_xor(Circuit(6).cx(0, 2).cx(1, 3), contract, backend="exhaustive")
assert faulty.status == "different" and faulty.witness is not None

See the table-XOR API guide for receipts and replay.

The HMR channel quantum input is arbitrary coherent data plus explicitly zero-prepared ancillas. A general Hadamard, rotation or reset program is not accepted by this sign-phase checker. The hybrid and cyclotomic reference engines have their own grammars. See the experimental guide, phases and composition.

Proof levels and replay

A positive answer is only as strong as the step that produced it. SymQ keeps these levels apart:

Level What it establishes Where
Engine decision SymQ computed equivalent for the declared theorem; trust rests on the engine (and on the SAT solver for SAT routes) Every checker
Replayed witness A claimed difference reproduces on concrete inputs, outside the symbolic engine Classical, table-XOR and channel differences
Replayed report A stored JSON report is recomputed from its embedded request; stored and fresh decisive results must match exactly symq replay, replay_table_xor
Independently checked formula proof For one opt-in research path (factored phase certificates), the obligation is encoded as a CNF and its UNSAT proof is exported as LRAT. A small standalone checker verifies it against a pinned CNF without a SAT solver, and a consumer rebuilds that CNF from the sources. In development CI, Lean's verified LRAT checker also proves selected instances. This certifies that CNF, not the source-to-CNF encoding or the quantum semantics symq.labs.lrat_rup, phase_proof_bundle, lrat_lean (details)
Lean theorems about an abstract model General theorems on Tseitin clauses, acyclic DAG evaluation, UNSAT soundness of the solver query shape and ripple-carry addition. Their statements and the model definitions are restated in checked contract files, so a weakened statement fails the build. They describe a model, which tests compare with the Python code formal/, development CI only (details)
Formal proof of SymQ itself Machine-checked correctness of the Python/C runtime or of its quantum semantics No

Passing tests, a green CI run or an agreeing second engine are evidence, not formal proof. A JSON receipt authorizes nothing until it is replayed. Its provenance (input-file digests, execution data) stays historical metadata that replay cannot authenticate.

Installation

Python 3.11 or newer (the 0.2 releases also support 3.10). A released version installs from PyPI:

python -m pip install symq          # add "symq[sat]" for the SAT engine

CPython 3.11 to 3.14 on Linux (x86-64 and arm64, glibc and musl) and on macOS (Intel and Apple silicon) get a wheel with the native C core. Everything else, Windows and free-threaded CPython included, gets the pure-Python package: the verdicts are the same, but the native engines are absent (--engine native is refused, auto uses the pure-Python zdd), so a budget can run out where the native core would have concluded. python -m symq doctor says which one is installed. For development, install from a source checkout:

git clone https://github.com/yoch/symq.git
cd symq
python -m venv .venv
source .venv/bin/activate
python -m pip install -e .
Installation Adds
python -m pip install -e ".[sat]" PySAT, for SAT contracts and contextual rewrites
python -m pip install -e ".[dev]" Tests, Ruff, mypy and the SAT development dependencies
python -m pip install -e ".[dev,external]" Optional PolyBoRi, CUDD and MQT QCEC comparison adapters
python -m pip install -e ".[test,crosscheck]" MQT QCEC alone, at the version the required cross-check job uses
Platform Native C core What CI runs on every change
Linux (x86-64) yes Whole suite on CPython 3.11 to 3.14; sanitizers; the cross-check against MQT QCEC
macOS (Apple silicon runner) yes Core tier on CPython 3.12
Windows (x86-64) no: pure Python only Core tier without the native tests on CPython 3.12

The core tier is the tests of symq, symq.sat, symq.backends, the repository guards and the runnable examples of the documentation; the tests of the experimental and research layers run on Linux only.

The native C/ZDD extension is optional. From a checkout or a source distribution it builds at install time when a compiler and the Python headers are present; a wheel from PyPI either contains it or does not. python -m symq doctor reports whether it loaded and why not. See getting started.

Limits

  • Exact does not mean unbounded. Unsupported gates, malformed contracts and exhausted budgets are refused or end inconclusive. An unfinished computation never establishes a difference, and inconclusive or unsupported is never turned into a proof.
  • Proof boundaries matter. Classical output equality is not channel equality. A channel that forgets outcomes is not an observed instrument. A dirty ancilla is never silently initialized to |0>.
  • Decomposition needs a proof. check_equivalence_by_blocks splits only classically disconnected circuits; a connected circuit is not decomposed without a separately proved interface contract.
  • Budgets are engine-specific. Term and node limits measure different data structures. A cooperative deadline is not an isolated-process limit, and max_bytes is not a process memory cap. See resource contracts.
  • Performance claims need matched tasks. Deciding equivalence, exporting ANFs and checking instruments are different jobs. No backend wins on every circuit; recorded measurements describe specific commits and workloads (evidence).

Documentation

Topic Document
First steps, native core Getting started, glossary, index
Backends, orders, blocks Backend guide
SAT contracts and relational cuts SAT guide
Contextual rewrites, preparation and replay Rewrite guide
Table-XOR loader contracts Public API, contract guide
Research modules, LRAT proofs, Lean model Labs index
HMR semantics HMR specification
Runnable scripts and CLI inputs examples/ (the Python scripts run in the test suite; the JSON inputs are exercised by CI), demo
Architecture, archive, history Architecture, archive index, changelog
Contributing and security CONTRIBUTING.md, code of conduct, AGENTS.md, SECURITY.md
Licenses of redistributed test and benchmark inputs Third-party notices

References

  • S. Minato, Zero-suppressed BDDs for set manipulation in combinatorial problems, DAC 1993: the monomial-set representation behind the ZDD backends.
  • A. Ignatiev, A. Morgado, J. Marques-Silva, PySAT: A Python toolkit for prototyping with SAT oracles, SAT 2018 (PySAT): the SAT engine.
  • L. Burgholzer, R. Wille, Advanced equivalence checking for quantum circuits, IEEE TCAD 2021 (MQT QCEC): the optional comparison adapter.
  • Qualtran (Apache-2.0): source of the pinned kickmix fixtures (provenance).
  • L. Cruz-Filipe, M. Heule, W. Hunt, M. Kaufmann, P. Schneider-Kamp, Efficient certified RAT verification, CADE 2017: the LRAT proof format.
  • L. de Moura, S. Ullrich, The Lean 4 theorem prover and programming language, CADE 2021: the proof assistant used in formal/.

Development

python -m pip install -e ".[dev]"
ruff check .
mypy
python -m pytest -q

SYMQ_TEST_REQUIRE=native,sat turns the skips of native- and sat-marked tests into errors. Changes should state their accepted grammar and theorem, add differential and adversarial tests, keep concrete witnesses, and report negative results with exact source and environment fingerprints.

MIT licensed · Research software · No general-purpose quantum certification claim.

Metadata

Release files for symq 0.4.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 symq 0.4.0
File Size Uploaded Provenance Actions
symq-0.4.0.tar.gz 1.6 MB With provenance Details for symq-0.4.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for symq 0.4.0
File Actions
symq-0.4.0-py3-none-any.whl Python 3 none any Details for symq-0.4.0-py3-none-any.whl
symq-0.4.0-cp314-cp314-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ x86-64 Details for symq-0.4.0-cp314-cp314-musllinux_1_2_x86_64.whl
symq-0.4.0-cp314-cp314-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ ARM64 Details for symq-0.4.0-cp314-cp314-musllinux_1_2_aarch64.whl
symq-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for symq-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
symq-0.4.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for symq-0.4.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
symq-0.4.0-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for symq-0.4.0-cp314-cp314-macosx_11_0_arm64.whl
symq-0.4.0-cp314-cp314-macosx_10_15_x86_64.whl CPython 3.14 CPython 3.14 macOS 10.15+ x86-64 Details for symq-0.4.0-cp314-cp314-macosx_10_15_x86_64.whl
symq-0.4.0-cp313-cp313-musllinux_1_2_x86_64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ x86-64 Details for symq-0.4.0-cp313-cp313-musllinux_1_2_x86_64.whl
symq-0.4.0-cp313-cp313-musllinux_1_2_aarch64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ ARM64 Details for symq-0.4.0-cp313-cp313-musllinux_1_2_aarch64.whl
symq-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for symq-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
symq-0.4.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for symq-0.4.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
symq-0.4.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for symq-0.4.0-cp313-cp313-macosx_11_0_arm64.whl
symq-0.4.0-cp313-cp313-macosx_10_13_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.13+ x86-64 Details for symq-0.4.0-cp313-cp313-macosx_10_13_x86_64.whl
symq-0.4.0-cp312-cp312-musllinux_1_2_x86_64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ x86-64 Details for symq-0.4.0-cp312-cp312-musllinux_1_2_x86_64.whl
symq-0.4.0-cp312-cp312-musllinux_1_2_aarch64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ ARM64 Details for symq-0.4.0-cp312-cp312-musllinux_1_2_aarch64.whl
symq-0.4.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for symq-0.4.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
symq-0.4.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for symq-0.4.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
symq-0.4.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for symq-0.4.0-cp312-cp312-macosx_11_0_arm64.whl
symq-0.4.0-cp312-cp312-macosx_10_13_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.13+ x86-64 Details for symq-0.4.0-cp312-cp312-macosx_10_13_x86_64.whl
symq-0.4.0-cp311-cp311-musllinux_1_2_x86_64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ x86-64 Details for symq-0.4.0-cp311-cp311-musllinux_1_2_x86_64.whl
symq-0.4.0-cp311-cp311-musllinux_1_2_aarch64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ ARM64 Details for symq-0.4.0-cp311-cp311-musllinux_1_2_aarch64.whl
symq-0.4.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for symq-0.4.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
symq-0.4.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for symq-0.4.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
symq-0.4.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for symq-0.4.0-cp311-cp311-macosx_11_0_arm64.whl
symq-0.4.0-cp311-cp311-macosx_10_9_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.9+ x86-64 Details for symq-0.4.0-cp311-cp311-macosx_10_9_x86_64.whl

Total release size: 15.7 MB

Release files / symq-0.4.0.tar.gz

Download URL symq-0.4.0.tar.gz
Size 1.6 MB
Tags Source
SHA-256 checksum
How to use checksums
21a79414e80ae146286ab4aa416af73c3b4d93f00e4f26b66612af9e8ae296be
BLAKE2b-256 checksum
How to use checksums
c9ede9206390f574dde98eb8cf729c2c556882ec4aeaa35539fdeb42b5018cee
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 13, 2026.

Transparency log

Release files / symq-0.4.0-py3-none-any.whl

Download URL symq-0.4.0-py3-none-any.whl
Size 534.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b37931ca70f641f0714b3e384d5f017e5f923e2d9d44a0ba947f35381ac57004
BLAKE2b-256 checksum
How to use checksums
b3e9246c3be1f9ab860f375abfdf585811e093513aec30e25b3a11cadae60997
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp314-cp314-musllinux_1_2_x86_64.whl

Download URL symq-0.4.0-cp314-cp314-musllinux_1_2_x86_64.whl
Size 567.2 kB
Tags CPython 3.14 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
9b6eae5cb945bd92d172ec7c3923bf1e5753396241c04ec3e93b561dd702a7eb
BLAKE2b-256 checksum
How to use checksums
797c839e146e306cc23e4f7b6ec739844edb16c865104bb45ed9d435b66dfb32
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp314-cp314-musllinux_1_2_aarch64.whl

Download URL symq-0.4.0-cp314-cp314-musllinux_1_2_aarch64.whl
Size 568.1 kB
Tags CPython 3.14 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
e091ada7e9c35fb9c13e390b487ab8b5c1252174009f1f58454e1ee2cbd9c505
BLAKE2b-256 checksum
How to use checksums
5a268c9a92f746f69bd81bc56606724997a51b99bd90270fabb28b5b23e064cb
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.4.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 566.6 kB
Tags CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
92bfd05d2dcedb233c778fe3f0e2fee3f1fc819cbc0cf5f706697651141bd6fe
BLAKE2b-256 checksum
How to use checksums
cc2867d3f45b939b703019ff1778adc7a28c896a0440ddeab2813d9c68dc6123
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.4.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 567.8 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
06c275dcd8c9ab154c9ad7bffe81d96d5155d6b3360c140546f9818d51d07d4f
BLAKE2b-256 checksum
How to use checksums
849c0f292dc07d95edf4e75ccae3d9be01e99fd42cb9c269152802d6a26883f5
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp314-cp314-macosx_11_0_arm64.whl

Download URL symq-0.4.0-cp314-cp314-macosx_11_0_arm64.whl
Size 559.6 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
ca45ed8bdeb9e71bbf4cd363adddd5b58e67a918febdd0337da2fd602c9be7fe
BLAKE2b-256 checksum
How to use checksums
0e34f47e7da7af72e426a3f67f95f8894fc495e10a0e582ce5244746f593fcec
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp314-cp314-macosx_10_15_x86_64.whl

Download URL symq-0.4.0-cp314-cp314-macosx_10_15_x86_64.whl
Size 560.6 kB
Tags CPython 3.14 macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
1d3fe2c69a8ef522fca9c06ee6990c8d6dd57a7ea67a5ae0af06482887aff02c
BLAKE2b-256 checksum
How to use checksums
068b8df21a4b1351db05990988ab57f964d694997497de7c1afad154449e074f
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL symq-0.4.0-cp313-cp313-musllinux_1_2_x86_64.whl
Size 567.3 kB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
5a674698c70edc69409563d99ca079253229bc62a5dadc55b0aa9139b1c8507d
BLAKE2b-256 checksum
How to use checksums
6dca098528fed13f17dc286b483f1bbce929d2c080760e8467408c219d6558e6
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp313-cp313-musllinux_1_2_aarch64.whl

Download URL symq-0.4.0-cp313-cp313-musllinux_1_2_aarch64.whl
Size 568.0 kB
Tags CPython 3.13 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
6a7d13089958ee9a76d4bd33eb31026eab5f9e23a3b353471f257c244595912d
BLAKE2b-256 checksum
How to use checksums
3cb8c4416c3fb2c9c91f75533282e542aa0592f9f034f110284b66019d66bc3a
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.4.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 566.7 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
fb6c36e6474dd0f08aab4035b47002b4d39a8d971f8e3e2735d62bf2a46bc29c
BLAKE2b-256 checksum
How to use checksums
3e5c2b97859e7ebf9f620ae1509f4e3f7c2d5474854bea9847ed6700acf48721
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.4.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 567.8 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
3ba77327621cb28dfb608389e15a442d0ab94ae76f5e98c1eb70a6bb7c8c52f3
BLAKE2b-256 checksum
How to use checksums
475a153c78c919b0fd46ff3d1b86813f66b0551f5351b3cd9a3937aaf30fbebe
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL symq-0.4.0-cp313-cp313-macosx_11_0_arm64.whl
Size 559.6 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
f750f1dafe186c5470ac3758890fe69284614a2b507aac2aa996b9f316715b67
BLAKE2b-256 checksum
How to use checksums
444073d972986b267b04e97a5782200add3a04538b56e2c7f5f1e6911b28a1d9
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp313-cp313-macosx_10_13_x86_64.whl

Download URL symq-0.4.0-cp313-cp313-macosx_10_13_x86_64.whl
Size 560.6 kB
Tags CPython 3.13 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
53e6d8cd560554b172c90f1f0f3bb652ad1aae6fff47a8564b17d095b214fb3d
BLAKE2b-256 checksum
How to use checksums
042c07fe4e310c6b60ecbb9fa4854ec2311bdfc5c8098e70f12dc60429bada23
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL symq-0.4.0-cp312-cp312-musllinux_1_2_x86_64.whl
Size 567.1 kB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
41969fad373998f409c5ebb0f557da92fba59d1afb097506f78d845e1967eaec
BLAKE2b-256 checksum
How to use checksums
6a11f638ff73c09808fc867616f3bc7e17ba8bd47195aa2f72d8b49ed9845029
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp312-cp312-musllinux_1_2_aarch64.whl

Download URL symq-0.4.0-cp312-cp312-musllinux_1_2_aarch64.whl
Size 567.9 kB
Tags CPython 3.12 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
c7a8c7d513d075e622b7ea4f9796c172d6b365d11281fba5ab0e31abb8b61392
BLAKE2b-256 checksum
How to use checksums
f87721d021d080667bd5cc69cf8d23f3f6e038139ff3dcf3fd9660afc92c25db
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.4.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 566.4 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
88f7ba18890dca95468ec859338740e19efa45345a626ae4294511228f5e0267
BLAKE2b-256 checksum
How to use checksums
3bd2a754fb1a1fe19d82ffe95320f95b6b0527867d6ad3e341d379221f66e4b5
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.4.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 567.6 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
7b290f18831e453791c06557be978cab9ed4655f0cb8f236749dcd8bf9c4d226
BLAKE2b-256 checksum
How to use checksums
eb6f76272a64cc0662704a689484874fcc4e0aa221eab0579d7e475661c22db3
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL symq-0.4.0-cp312-cp312-macosx_11_0_arm64.whl
Size 559.6 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
4a098e7062bd6be13f448c3bc7d8481bfd7d76d95b40fda469a2d7f1583cbf05
BLAKE2b-256 checksum
How to use checksums
7a773145c8aefc51ac81d9b65ac88f5246248e565cdac9214c3acbe7679805c1
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp312-cp312-macosx_10_13_x86_64.whl

Download URL symq-0.4.0-cp312-cp312-macosx_10_13_x86_64.whl
Size 560.5 kB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
37d095bc2f182a9def669de74f00be98187b5371bfb0e070add8462e6eb902de
BLAKE2b-256 checksum
How to use checksums
ee75499f8d685a42620fe35c2e81cce9d8292b1352dbdaf21ef26d9336857f81
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL symq-0.4.0-cp311-cp311-musllinux_1_2_x86_64.whl
Size 566.3 kB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
96af5721de6ec377f029c250f20152051f79a19762331855eb086651aa741a1f
BLAKE2b-256 checksum
How to use checksums
23bf2ea72436e543318184a8b64a7828085e3bc8fdb436b3485a7907b819351b
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp311-cp311-musllinux_1_2_aarch64.whl

Download URL symq-0.4.0-cp311-cp311-musllinux_1_2_aarch64.whl
Size 567.1 kB
Tags CPython 3.11 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
1d14ec6d0135614bf0d1794d752dbf9c43caf30520a437083fea65bc2cba220f
BLAKE2b-256 checksum
How to use checksums
0d16c843bbdffe3a34b8ec73b73483b5e59d3c08b84d70543903891523195f9c
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL symq-0.4.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 565.6 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
d260ad78c5d43f815ec2d5034b364ff26e066386156a6077522784f4df4339a9
BLAKE2b-256 checksum
How to use checksums
72e2208bf331c027ea53cadbeb509d40c5a73158191ab46abe4460edc29c80a7
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL symq-0.4.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 566.7 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
028659b174a40b66f21c871583651f0918d3abc4e0fd1870f0c8318ff50be6e2
BLAKE2b-256 checksum
How to use checksums
cdd31130e7638ade80daa395c31ffec9dfa01f852b9599fb1546cc8e2e9b3735
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL symq-0.4.0-cp311-cp311-macosx_11_0_arm64.whl
Size 558.8 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
ebf50504b61aa6cf9a70950206a55ac0eaba5c648952ad14f7605c2b0a719bbf
BLAKE2b-256 checksum
How to use checksums
b1c035721189a2c00ea1fece1f58dc1e071101950d8b8e22a06df8240e6d1c08
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 13, 2026.

Transparency log

Release files / symq-0.4.0-cp311-cp311-macosx_10_9_x86_64.whl

Download URL symq-0.4.0-cp311-cp311-macosx_10_9_x86_64.whl
Size 559.2 kB
Tags CPython 3.11 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
b586e9ece7882c9cb3f3bb8938a85665790b54c0310a0480e0a4e5ca8b0efb12
BLAKE2b-256 checksum
How to use checksums
4654cf981d57b1496221bce17252a589c42d99426dc081f2b7772759fbfdd9cf
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 13, 2026.

Transparency log

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

Select from 26 files

Attestation for symq-0.4.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 13, 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