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

Built distributions (wheels)

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

Total release size: 15.6 MB

Release files / symq-0.3.0.tar.gz

Download URL symq-0.3.0.tar.gz
Size 1.6 MB
Tags Source
SHA-256 checksum
How to use checksums
febd9e2e15791b831be46207168c157a90e686491626c9f43ba41e1886d37928
BLAKE2b-256 checksum
How to use checksums
54d36393772428aeea50b44b347b8a9efb3cdf493c52e91ae3f42abf2069681f
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-py3-none-any.whl
Size 530.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4e8384450fa79c59a7ced111f05ffc29ff6d3fb88c17b8075c17702c74e968bf
BLAKE2b-256 checksum
How to use checksums
4002c61ee3b52ee8738ddc687ca1e2643d2bb3e5d345d0ac91f4f9eed13e95e0
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp314-cp314-musllinux_1_2_x86_64.whl
Size 563.3 kB
Tags CPython 3.14 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
4a4a2ced71bdcfd8759ca3076ffab0ffae70e9d464905919ae7be70418187aa3
BLAKE2b-256 checksum
How to use checksums
5c37d2cb29c482e0115e5815380acbeed90b50b345f8af4f282caba3665a4f4f
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp314-cp314-musllinux_1_2_aarch64.whl
Size 564.1 kB
Tags CPython 3.14 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
589572363629ea8fd3c0fb16e7e0f9f19efdaa187b6b1cd88cda3d9f572b9ebc
BLAKE2b-256 checksum
How to use checksums
2501d517d77a4902da4d5697e811347a5fa373a6e8616ca47e3d29780ec781eb
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 562.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
226f865ad605279d5b04efa79911bda7b8e0347e5a61e1f61cf4d6608e3635f3
BLAKE2b-256 checksum
How to use checksums
e161da277abed4e50dbbe86b6bd9d318ca5938c3f0c57479c6ff0d0a590ac99c
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 563.8 kB
Tags CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
cf26fe8291360b76247cfecd4caad2447892dc529f53dd0d81a504546fa96b5f
BLAKE2b-256 checksum
How to use checksums
74d980d986f680d0ee76ca9ea220de06991508d14eecaa93b90c12620ee461d6
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp314-cp314-macosx_11_0_arm64.whl
Size 555.7 kB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
f0b6d98598252441c636c38fcf7ac273354b6a27f40d73ff961c4f916d5c6bd8
BLAKE2b-256 checksum
How to use checksums
77ae74674275c466feb84e0ff9dbff881d3e732975efc868a3c803f557deb9d3
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp314-cp314-macosx_10_15_x86_64.whl
Size 556.6 kB
Tags CPython 3.14 macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
bde08dbabbf81ef58b3c9eef82cc961a20917656b3c4a085bc9c68d62f4c6dad
BLAKE2b-256 checksum
How to use checksums
2b79f6ddb4e8e56083700067d08e7d74281c1047a46580ff5f23f0da9cfac4e0
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp313-cp313-musllinux_1_2_x86_64.whl
Size 563.3 kB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
1375cbd30a0b1e3e65ffb6f133700e2280b1fda6ea3fe3ba29d0767612b1a90c
BLAKE2b-256 checksum
How to use checksums
8238c9f5fc7b19000b6ad51fcd9f96d81eda83990a73f99e9efa9a9005ef5288
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp313-cp313-musllinux_1_2_aarch64.whl
Size 564.1 kB
Tags CPython 3.13 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
e4bf4a25b47719a135fd4d5f49f0552bf04096cde6c2600a1448caa3dd9bf4d6
BLAKE2b-256 checksum
How to use checksums
f2f0679df616b2cdf71843d6d8e00fe1422d976f5f344029c6185f0cc0dac634
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 562.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
a026a86d97575275f96f677c0a117b327c00adf1fae918705bf436cf6baa8e6a
BLAKE2b-256 checksum
How to use checksums
2e6d3f4b9da0a87d9c4b47fa09bbe8fcb623580aab6d65c0817d178e8bd075c6
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 563.8 kB
Tags CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
465163638d3abf7440b86096ce68e639277444eaa693e1bc86285e2c14181bb7
BLAKE2b-256 checksum
How to use checksums
fc5f6789ff007668eb1e00e5b217cce3c01812bcee4400b8b6aaa9d0f3994555
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp313-cp313-macosx_11_0_arm64.whl
Size 555.7 kB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
00cf927a01f660b13bf7351be42d8cab3c13d7fdcc8b5b401d1a90aad58b68f0
BLAKE2b-256 checksum
How to use checksums
3abbfa607d444abab5b5b44de047e8fe0085a44adb690eafe4d8be5c130edad6
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp313-cp313-macosx_10_13_x86_64.whl
Size 556.6 kB
Tags CPython 3.13 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
6e9d6774667a17c5e8f8151795e2e7ba652f927f152318d1670389d4c9bf2a06
BLAKE2b-256 checksum
How to use checksums
a5676855b23cf4efc8d13b467c04b6c6e0ac76d9d9cd0d5cea37b9ff4d0c8809
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp312-cp312-musllinux_1_2_x86_64.whl
Size 563.2 kB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
abcbe41bfd390f9c9837577f90e2f17ad3213b60f531678cdd5bc1e43777d51f
BLAKE2b-256 checksum
How to use checksums
591d3fc65fe82529203ab5a993a084e09fc22eed7262077ffa3062fef842e6f9
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp312-cp312-musllinux_1_2_aarch64.whl
Size 563.9 kB
Tags CPython 3.12 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
df3d7ad650f4bc4dbf821b92e19519cd25fbdaf69a325e39b9f53285b4422882
BLAKE2b-256 checksum
How to use checksums
bf4494f0418ea877c37a28bc4263c7fdc2a3c9414b8bc5c7ed9e58080f4d87e4
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 562.5 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
3a1e310264893d5fba24ac6cbbbd2892388dd802c433256fe8c1c12677cac53b
BLAKE2b-256 checksum
How to use checksums
0888a0bfe5094d0f3455b211a33a559c5e0b979efe29816870860d07d61f55f5
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 563.6 kB
Tags CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
9037a44c7a0d5e7a1d8247c986e660b5e1affb442c6af4bb16f79808ed373844
BLAKE2b-256 checksum
How to use checksums
a7aa4db0b2ba949734daf1f6a133a07f48852ccdc21e8cc2feef0a954ac651aa
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp312-cp312-macosx_11_0_arm64.whl
Size 555.6 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
cad3096e8c4991e54b43d2a2fe8e0eadb88bc3531820a67ea444914b53e2e8b8
BLAKE2b-256 checksum
How to use checksums
617712fde0bf33d9f25f6795bd4cd1452729b5945faa3f37ccb9790051aa8d5c
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp312-cp312-macosx_10_13_x86_64.whl
Size 556.6 kB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
65293b867cb39f23778f2c624a21d54857ffa05af73def5b8dcf8b33dc4d9fc5
BLAKE2b-256 checksum
How to use checksums
5c71fd3ad5504ef3dcd8b5855b2d757b71c57e6da6786d081b8741e0b3fc1331
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp311-cp311-musllinux_1_2_x86_64.whl
Size 562.3 kB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
b790617d9692159647754b4f044c0966e23944fe7ffd45f758da5ef67543d1a0
BLAKE2b-256 checksum
How to use checksums
643f34c03df6a7980d6848541d3e2a81acf0511fa0e3ef446f77c90d323a1c84
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp311-cp311-musllinux_1_2_aarch64.whl
Size 563.1 kB
Tags CPython 3.11 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
21debd11e1230a5e7d234c730454036699a7d7f9c0cf97e860ecc6538736672f
BLAKE2b-256 checksum
How to use checksums
9eb591c30e883d7b0f73cc142f3def4bc2daf146bfdd1db91847907cd4a9ef37
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 561.7 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
0b250dee3fd4a63a59696f3384e9e8820c7b5ee9cdd182c74809bece67560cf6
BLAKE2b-256 checksum
How to use checksums
6a71c42741ebf29e26126bcb474e2ad2f723fe9a3a4aa340c07c9829bdee2e28
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 562.8 kB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
e7ad095b7fd02d9c5de481c3954ed2d57659f3f2bbb357045be2a710865e7c76
BLAKE2b-256 checksum
How to use checksums
43020a5aa26fff7532a835b1c9239a67e4d7d0ab77afdaf6ad50992404f78b7f
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp311-cp311-macosx_11_0_arm64.whl
Size 554.8 kB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
c36da9299a73a9d010bb7382775031111790028c18be87434f88737ef38185fb
BLAKE2b-256 checksum
How to use checksums
669d0ba5ce6d7371a6f0225d5dbf636187dda9b973dfaa5b1132b21d6a446999
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 12, 2026.

Transparency log

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

Download URL symq-0.3.0-cp311-cp311-macosx_10_9_x86_64.whl
Size 555.2 kB
Tags CPython 3.11 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
478e9a3de43f91828980c220e5577bfd69979f87bc73fcd53fbcf4278df93785
BLAKE2b-256 checksum
How to use checksums
ac300424e69492f2626980ca24584cfc04b42790d0f9cb4bf60198d269b01954
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 12, 2026.

Transparency log

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

Select from 26 files

Attestation for symq-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 12, 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