Skip to main content

SoftQCOS CLI

PyPI version Python 3.10+ License: Proprietary

The softqcos command talks to the QCOS REST API at https://api.softquantus.com. It has no privileges of its own: every command is a call to /api/v1/* made with your API key, and runs only what that API serves.

The CLI, the Python SDK (softqcos-sdk) and the MCP server (softqcos-mcp) are released together and always carry the same version number. The table at the end of this page lists what each version added.

Install

pip install softqcos
softqcos --version

The PyPI package is softqcos; it installs softqcos-sdk as a dependency. Python 3.10 or newer. Every command, including offline softqcos verify of RSA-PSS and Ed25519 seals, works from that plain install.

The extras forward to the SDK's:

pip install "softqcos[simulation]"   # Qiskit + Aer: run circuits locally
pip install "softqcos[pqc]"          # liboqs-python: verify ML-DSA (FIPS 204) seals
pip install "softqcos[all]"          # every SDK extra (qiskit, cirq, pennylane, ibm, braket, azure, pqc)

pqc installs liboqs-python, which is only the binding: the native liboqs shared library must be installed too, either by running python -c "import oqs" once (it downloads and builds liboqs into ~/_oqs; needs git, cmake and a C compiler) or by setting OQS_INSTALL_PATH to the prefix of a shared build. softqcos evidence verify never builds it for you; without it an ML-DSA seal reports signature_valid: None, with the reason.

Sign in

Create an API key at https://platform.softquantus.com/#apikeys, then:

softqcos auth login

auth login asks for the key, checks that https://api.softquantus.com/api/v1/status answers, and saves both in ~/.softqcos/config.json (file mode 0600). In CI, skip the file and set the environment instead:

export QCOS_API_KEY="<your key>"

Settings are resolved in this order: environment variable, then ~/.softqcos/config.json, then the default.

Setting Environment variable Default
API key QCOS_API_KEY none
API URL QCOS_API_URL https://api.softquantus.com
Platform URL QCOS_PLATFORM_URL https://platform.softquantus.com
softqcos config                      # show what is stored
softqcos config set api_url https://api.softquantus.com
softqcos config --reset              # delete ~/.softqcos/config.json
softqcos auth status                 # key and license status
softqcos auth logout                 # release the local license

softqcos doctor checks the config file, the URLs, that a key is present, and that the API answers GET /api/v1/status. That route does not need a key, so a passing doctor does not prove the key is valid. The first authenticated command does.

First job, on a simulator

Save a Bell circuit as bell.qasm:

OPENQASM 2.0;
include "qelib1.inc";
qreg q[2];
creg c[2];
h q[0];
cx q[0],q[1];
measure q -> c;

Ask for an estimate first. --dry-run executes nothing:

softqcos jobs submit --circuit bell.qasm --backend simulator_aer --shots 1024 --dry-run

Then submit, and read the result with the job id it prints:

softqcos jobs submit --circuit bell.qasm --backend simulator_aer --shots 1024
softqcos jobs status <job_id>
softqcos jobs results <job_id>
softqcos jobs list --limit 5

--backend defaults to simulator_aer. A QPU backend costs money: pass --confirm-cost once you have read the estimate. Spend ceilings are not set here: QCOS does not price workloads, so --max-cost-usd is refused. Set the ceiling on the SoftQuantus Platform with max_estimated_cost_usd on POST https://platform.softquantus.com/api/v1/platform/execution/jobs. Every command takes --json for scripts.

Commands

softqcos --help lists the root commands; every group has its own --help.

Command What it does
auth login, status, logout, license
config show, set, --reset the local config
doctor local config and API reachability
info, version, welcome environment, version, product overview
jobs submit, status, results, list, cancel, approve, evidence, bundle, events, verify
circuits circuit management, optimization, simulation, targets, inspect (compile only)
algorithms Shor, Grover, QFT, QPE, QAOA and the other algorithm runners
backends your own backend credentials (bring your own backend)
billing pricing and ROI estimates
webhooks HMAC-signed job events pushed to your endpoint
research preregistered studies, evidence and claims
verify verify an evidence record offline: softqcos verify record.json --trust-bundle bundle.json (exit 0 valid, 1 invalid, 2 unreadable)
api JSON-first commands for agents and automation (below)
generate seeded content generation with entropy provenance (below)
extensions 32 specialised domains: softqcos extensions --help
license activate, status, deactivate
srp Research Package runtime, see the note below

softqcos extensions holds the specialised domains: qec, network, calibration, chemistry, state, dynamics, evidence, qubo, science, hybrid and more. Each of them also answers at the root (softqcos qec ...) for older scripts. Those root aliases are not listed in --help. New scripts should use softqcos extensions <group>.

Removed in 3.9.2: admin, macro, autopilot, nvqlink and zne. Every one of their commands called a route the API does not serve, so each answered 404.

softqcos srp needs the softqcos[srp] extra. That extra depends on softqcos-srp, which is not published on PyPI yet, so pip install "softqcos[srp]" fails today.

softqcos api

Stable JSON-first commands for agents, MCP bridges, Cursor, Copilot, and scripts:

softqcos api workspace init --json
softqcos api workspace discover --json
softqcos api job validate --input jobs/bell.qcos.json --json
softqcos api job plan --input jobs/bell.qcos.json --json
softqcos api run local --input jobs/bell.qcos.json --json
softqcos api result summary --input results/<run_id>/summary.json --json

These commands return structured payloads with status, capability, artifacts, metrics, and next_actions so AI agents can continue workflows reliably.

QCOS GPU planning commands:

softqcos api gpu detect --json
softqcos api gpu benchmark --input circuits/bell.qasm --json
softqcos api gpu engine-detect --json
softqcos api gpu estimate-memory --qubits 30 --precision fp64 --json
softqcos api gpu plan --input circuits/bell.qasm --json
softqcos api gpu simulate --input circuits/bell.qasm --fallback-aer --json
softqcos api backend plan --input circuits/bell.qasm --json
softqcos api backend compare --input circuits/bell.qasm --execute-aer --json
softqcos api hybrid detect --json
softqcos api hybrid qec-plan --code surface --distance 5 --rounds 3 --json
softqcos api qlink plan-feedback-loop --qpu lab-qpu-1 --latency-budget-us 100 --qec --json

softqcos generate

Structured content for games, design tools and simulations, expanded from a seed the runtime draws. The expansion is a named deterministic function, so anyone holding the seed digest can reproduce the output; nothing here is computed on a QPU and nothing here is faster because of quantum.

softqcos generate tasks
softqcos generate seed --seed-bytes 32
softqcos generate terrain --width 64 --height 64 --biomes 4
softqcos generate character --personality 8 --traits 8 --relationships 3
softqcos generate narrative-branch -o ally -o betray --weight 1 --weight 3
softqcos generate distribution --samples 1000 --shape normal

Every successful run prints where the entropy came from — the backend that answered, whether it was genuinely quantum, and the seed digest:

Provenance
  backend        cloud_ibm
  quantum        yes — a quantum source produced the seed
  entropy_bits   256.0
  expander       splitmix64/v1
  seed_sha256
    a1a1...

--quantum-required refuses classical entropy instead of substituting it: if no quantum source answers, the command fails, nothing is generated, and the error says so. Use it whenever the origin of the result will be claimed publicly.

softqcos generate terrain --quantum-required     # exits non-zero if no QPU entropy
softqcos generate terrain --json                 # full response, provenance included

softqcos extensions science

The Scientific Runtime (experimental): one contract for a scientific problem, a planner that says which solver fits it, and a result that carries its own validation. The algorithms are entries of one catalog, not separate products.

softqcos extensions science capabilities
softqcos extensions science algorithms --capability eigensolve --status available
softqcos extensions science algorithms --experimental-quantum
softqcos extensions science plan eigensolve --model transverse_field_ising --sites 4 --field 1.0 --tolerance 1e-3
softqcos extensions science eigensolve --model transverse_field_ising --sites 4 --field 1.0 --n-states 2
softqcos extensions science eigensolve --model transverse_field_ising --sites 4 --field 1.0 --algorithm vqe --seed 7
softqcos extensions science evolve --model transverse_field_ising --sites 4 --field 1.0 --total-time 2.0 --observable Z0=ZIII
softqcos extensions science optimize --problem qubo.json
softqcos extensions science simulate --model fermi_hubbard --sites 2 --interaction 4.0 --particle-number 2 --total-time 1.0
softqcos extensions science resource-estimate --model transverse_field_ising --sites 4 --field 1.0 --tolerance 1e-3
softqcos extensions science validate --model transverse_field_ising --sites 4 --field 1.0 --claimed-value -4.7588 --tolerance 1e-3

A problem is a JSON object: --problem FILE (- reads stdin), or a lattice model described with --model and --sites. A flag overrides the same field of the file. qubo.json above is {"qubo": {"linear": [-1.0, -2.0, 1.0], "quadratic": [[0, 1, 3.0], [1, 2, -2.0]]}}.

Every computation prints its verdict first:

eigensolve  algorithm=vqe  substrate=local_cpu_statevector  qubits=4  runtime=5.145139 s
validation: FAILED  |error|=0.01426626188  tolerance=1e-06  reference=exact_diagonalization

That run is the sixth command above, and the verdict is the point: the hardware-efficient ansatz at its default depth stops 1.4e-2 above the exact ground energy, and the runtime says so instead of returning a number that looks like an answer. A result that misses its tolerance is still a result — the API answers 200 and the command exits 0; read the status, or pass --json.

Nothing here reaches a QPU or a GPU. The quantum algorithms run on the API host's exact statevector simulator (16 qubits by default; capabilities prints the limits). plan lists what a problem would cost on hardware without running it. The catalog is larger than what executes: entries marked planned, experimental_quantum (VQLS, HHL, amplitude estimation) or resource_estimate_only (QPE, qubitization) are refused with the list of algorithms that do run. The catalog and the planner need a key with qcos:read; the computations need qcos:execute.

softqcos extensions hybrid

Hybrid Workflows (experimental): a hybrid.workflow.v1 document describes a DAG of cpu and quantum tasks, optional bounded loops with a convergence rule, and a budget. The server's engine (Qoracle) places each task only on an executor that has demonstrated the operation, runs ready tasks concurrently and checkpoints every loop iteration.

softqcos extensions hybrid capabilities
softqcos extensions hybrid submit bell.json --wait
softqcos extensions hybrid status hwf_3e0fd003b7bc46c2aa78ae5e46c1f752
softqcos extensions hybrid reconcile <workflow_id> --run-key <run_key> --remote-job-id <job id>
softqcos extensions hybrid reconcile <workflow_id> --run-key <run_key> --not-submitted

bell.json samples a Bell pair 1000 times in the ZZ basis:

{"schema": "hybrid.workflow.v1", "name": "bell",
 "tasks": [{"id": "bell", "kind": "quantum", "operation": "quantum.sample",
            "params": {"qasm_template": "OPENQASM 2.0;\ninclude \"qelib1.inc\";\nqreg q[2];\nh q[0];\ncx q[0],q[1];\n",
                       "basis": "ZZ", "shots": 1000},
            "execution_mode": "simulator", "budget": {"max_shots": 1000}}],
 "budget": {"max_total_shots": 1000}, "outputs": ["bell"]}

The second command above, run against a local API on 2026-10-15:

hwf_3e0fd003b7bc46c2aa78ae5e46c1f752  status=succeeded
┃ run key ┃ state     ┃ attempts ┃ executor          ┃ remote job ┃ error ┃
│ bell    │ succeeded │ 1        │ local_statevector │ —          │       │
Outputs (provenance included; use --json for every field)
  bell: {"basis": "ZZ", "counts": {"00": 502, "11": 498}, "n_qubits": 2, "provenance": {"execution_type": "simulator", "migration_debt": "ADR 0004 D5", "resource": "local_statevector", "sampler": "multinomial over exact statevector probabilities", "seed": "8921458263615337965"}, "requested_shots": 1000, "shots": 1000}

submit --wait exits 0 when the workflow succeeds, 1 when it fails, 3 when it is blocked and 4 when --timeout runs out while it keeps running on the server. A refusal is printed in the engine's own words, with exit 1:

Error (gpu_executor_not_demonstrated): task g needs a GPU; no GPU executor has been demonstrated, and a GPU task is never run on a CPU instead
  task_id: g

No GPU executor has been demonstrated, so a gpu task is refused, never moved to a CPU. Quantum hardware is reached only through Softquantus Cloud when the API runs with that lane on; otherwise quantum tasks run on the API host's exact statevector simulator, and their provenance says so. There is no Platform authoriser yet: a workflow that would use a billable executor is refused with 403 authorization_required. A quantum submission whose outcome is uncertain is never resubmitted; the workflow stops in blocked until reconcile gives exactly one answer. Each submit creates a new workflow, so do not retry one blindly. capabilities and status need qcos:read; submit and reconcile need qcos:execute.

What each version added

Generated from the code at release time, so it cannot drift from what this version runs. Command paths as you type them.

Package version on this source tree: 3.15.1. softqcos-sdk, softqcos and softqcos-mcp always carry the same number, so the row a name sits in is the first version of THIS package that has it. A version is listed once it is tagged; it reaches PyPI when that release is published, and pip index versions softqcos shows which versions PyPI has.

Version Added
3.15.1 softqcos circuits inspect, softqcos circuits targets, softqcos lang, softqcos lang check, softqcos lang compile, softqcos lang invocations, softqcos lang invoke, softqcos lang programs, softqcos lang publish, softqcos lang run, softqcos lang synthesize
3.14.0 softqcos extensions science steady-state
3.13.0 softqcos extensions hybrid, softqcos extensions hybrid capabilities, softqcos extensions hybrid reconcile, softqcos extensions hybrid status, softqcos extensions hybrid submit
3.12.0 softqcos extensions qec lint-dem, softqcos extensions qec resource-tree
3.11.0 softqcos extensions science sim, softqcos extensions science sim export, softqcos extensions science sim graph, softqcos extensions science sim graph-plan, softqcos extensions science sim jobspec, softqcos extensions science sim physics, softqcos extensions science sim plan, softqcos extensions science sim resolve, softqcos extensions science sim run, softqcos extensions science sim solver, softqcos extensions science sim solvers, softqcos extensions science sim surrogate
3.10.0 softqcos extensions science, softqcos extensions science algorithm, softqcos extensions science algorithms, softqcos extensions science capabilities, softqcos extensions science eigensolve, softqcos extensions science evolve, softqcos extensions science optimize, softqcos extensions science plan, softqcos extensions science resource-estimate, softqcos extensions science simulate, softqcos extensions science validate
3.9.2 softqcos billing report-data
3.9.0 softqcos evidence get, softqcos evidence list, softqcos evidence runtime, softqcos evidence trust, softqcos extensions evidence runtime, softqcos extensions hal, softqcos extensions hal backend, softqcos extensions hal backends, softqcos extensions hal cancel, softqcos extensions hal result, softqcos extensions hal status, softqcos extensions hal submit, softqcos extensions research-apps, softqcos extensions research-apps get, softqcos extensions research-apps list, softqcos extensions research-apps molecular-vqe, softqcos extensions research-apps molecular-vqe run, softqcos extensions research-apps plan, softqcos quantus, softqcos quantus advantage, softqcos quantus analyze, softqcos quantus backends, softqcos quantus build, softqcos quantus coefficient, softqcos quantus compile, softqcos quantus evidence, softqcos quantus execute, softqcos quantus explain, softqcos quantus get, softqcos quantus lifecycle, softqcos quantus normalize, softqcos quantus rules, softqcos quantus seal, softqcos quantus store, softqcos quantus suitability, softqcos quantus validate, softqcos srp, softqcos srp compare, softqcos srp init, softqcos srp inspect, softqcos srp run, softqcos srp status, softqcos srp validate
3.8.3 softqcos extensions evidence, softqcos extensions evidence get, softqcos extensions evidence list, softqcos extensions evidence trust, softqcos extensions evidence verify
3.8.2 softqcos extensions dynamics, softqcos extensions dynamics analyze, softqcos extensions state, softqcos extensions state analyze
<=3.8.0 329 commands, all present in 3.8.0, the first version of the shared numbering

Removed (no longer exists):

  • softqcos admin: since <=3.8.0, removed in 3.9.2
  • softqcos admin audit: since <=3.8.0, removed in 3.9.2
  • softqcos admin backends-status: since <=3.8.0, removed in 3.9.2
  • softqcos admin circuit-breakers: since <=3.8.0, removed in 3.9.2
  • softqcos admin config: since <=3.8.0, removed in 3.9.2
  • softqcos admin health: since <=3.8.0, removed in 3.9.2
  • softqcos admin logs: since <=3.8.0, removed in 3.9.2
  • softqcos admin metrics: since <=3.8.0, removed in 3.9.2
  • softqcos admin rate-limits: since <=3.8.0, removed in 3.9.2
  • softqcos admin tenants: since <=3.8.0, removed in 3.9.2
  • softqcos admin usage: since <=3.8.0, removed in 3.9.2
  • softqcos evidence artifacts: since <=3.8.0, removed in 3.8.3
  • softqcos evidence capabilities: since <=3.8.0, removed in 3.8.3
  • softqcos evidence download: since <=3.8.0, removed in 3.8.3
  • softqcos evidence public-key: since <=3.8.0, removed in 3.8.3
  • softqcos extensions autopilot: since <=3.8.0, removed in 3.9.2
  • softqcos extensions autopilot execute: since <=3.8.0, removed in 3.9.2
  • softqcos extensions autopilot plan: since <=3.8.0, removed in 3.9.2
  • softqcos extensions autopilot recommend: since <=3.8.0, removed in 3.9.2
  • softqcos extensions autopilot vendors: since <=3.8.0, removed in 3.9.2
  • softqcos extensions macro: since <=3.8.0, removed in 3.9.2
  • softqcos extensions macro energy-optimize: since <=3.8.0, removed in 3.9.2
  • softqcos extensions macro health: since <=3.8.0, removed in 3.9.2
  • softqcos extensions macro market-sizing: since <=3.8.0, removed in 3.9.2
  • softqcos extensions macro risk-analysis: since <=3.8.0, removed in 3.9.2
  • softqcos extensions provider-hub list: since <=3.8.0, removed in 3.9.2
  • softqcos extensions provider-hub register: since <=3.8.0, removed in 3.9.2
  • softqcos extensions provider-hub remove: since <=3.8.0, removed in 3.9.2
  • softqcos extensions qlink: since <=3.8.0, removed in 3.9.2
  • softqcos extensions qlink profile: since <=3.8.0, removed in 3.9.2
  • softqcos extensions qlink simulate: since <=3.8.0, removed in 3.9.2
  • softqcos extensions qlink status: since <=3.8.0, removed in 3.9.2
  • softqcos extensions qlink transfer: since <=3.8.0, removed in 3.9.2
  • softqcos extensions qubo energy-dispatch: since <=3.8.0, removed in 3.9.2
  • softqcos extensions qubo portfolio: since <=3.8.0, removed in 3.9.2
  • softqcos extensions zne: since <=3.8.0, removed in 3.9.2
  • softqcos extensions zne mitigate: since <=3.8.0, removed in 3.9.2

License

Closed commercial software. This package is licensed, not sold, under the SoftQuantus Software License Terms v2.0 (SPDX LicenseRef-SoftQuantus-Proprietary-2.0); the full text is the LICENSE file in the distribution. It is not open source: it ships as compiled wheels only, with no source distribution. Versions 3.13.1 and earlier were published under Apache-2.0, and that grant stays with those versions.

Copyright © 2024-2026 SoftQuantus innovative OÜ. All Rights Reserved. Registry code 17048927, Narva mnt 5, 10117 Tallinn, Estonia. QCOS™ and SoftQuantus™ are trademarks of SoftQuantus innovative OÜ. The QCOS service reached through this package is governed by the SoftQuantus Terms of Service.

Company

SoftQuantus innovative OÜ Registry Code: 17048927 Address: Narva mnt 5, Tallinn, 10117, Estonia

Contact


© 2024-2026 SoftQuantus innovative OÜ. All Rights Reserved. QCOS™ is a trademark of SoftQuantus innovative OÜ.

Metadata

Release files for softqcos 3.15.1

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

Built distributions (wheels)

Table of built distributions (wheels) for softqcos 3.15.1
File Actions
softqcos-3.15.1-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for softqcos-3.15.1-cp314-cp314-win_amd64.whl
softqcos-3.15.1-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 softqcos-3.15.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
softqcos-3.15.1-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for softqcos-3.15.1-cp314-cp314-macosx_11_0_arm64.whl
softqcos-3.15.1-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for softqcos-3.15.1-cp313-cp313-win_amd64.whl
softqcos-3.15.1-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 softqcos-3.15.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
softqcos-3.15.1-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for softqcos-3.15.1-cp313-cp313-macosx_11_0_arm64.whl
softqcos-3.15.1-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for softqcos-3.15.1-cp312-cp312-win_amd64.whl
softqcos-3.15.1-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 softqcos-3.15.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
softqcos-3.15.1-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for softqcos-3.15.1-cp312-cp312-macosx_11_0_arm64.whl
softqcos-3.15.1-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for softqcos-3.15.1-cp311-cp311-win_amd64.whl
softqcos-3.15.1-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 softqcos-3.15.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
softqcos-3.15.1-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for softqcos-3.15.1-cp311-cp311-macosx_11_0_arm64.whl
softqcos-3.15.1-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for softqcos-3.15.1-cp310-cp310-win_amd64.whl
softqcos-3.15.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for softqcos-3.15.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
softqcos-3.15.1-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for softqcos-3.15.1-cp310-cp310-macosx_11_0_arm64.whl

Total release size: 24.1 MB

Release files / softqcos-3.15.1-cp314-cp314-win_amd64.whl

Download URL softqcos-3.15.1-cp314-cp314-win_amd64.whl
Size 1.3 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
c11ab121819743e61fbee2b1bb4079242a7bd39725d33384973870c736719693
BLAKE2b-256 checksum
How to use checksums
27b13da3333564fd3dab1ef8c264f96aff7c7871fadc4f93ac9e00735f3f809b
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL softqcos-3.15.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.2 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
fd2bf3cf3b9521326b7b015828c6ef600e99b43bb8f5d7df884c80d496704444
BLAKE2b-256 checksum
How to use checksums
e2e6604ac8de3583e5d4808f4f3cda7c2c9677fb6f97e47f67fb1f593373069d
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp314-cp314-macosx_11_0_arm64.whl

Download URL softqcos-3.15.1-cp314-cp314-macosx_11_0_arm64.whl
Size 1.6 MB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
abf4b7d4372f7c7cbde265c37d4001d5cc1895149bd1b1a621baa41f3a4186d4
BLAKE2b-256 checksum
How to use checksums
17265987a7fab008dc3249086bb592b0143db6dac157dd674addadf29d85d84c
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp313-cp313-win_amd64.whl

Download URL softqcos-3.15.1-cp313-cp313-win_amd64.whl
Size 1.3 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
0d854c8b91373c6d93c9e879f4c366ca9f7463437aaf9770c9cd1014fcbe30d2
BLAKE2b-256 checksum
How to use checksums
7be65b202eb5808b23a506413f51de0919ed043208c741a3574230b910ec1d0b
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL softqcos-3.15.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.1 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
8aba8d45217d75692a1d1517020dbdba63eafc8efc40f02b3afa179cf3da5668
BLAKE2b-256 checksum
How to use checksums
91edba7d3e32bdaf2f940869743c9676856c0d14ac0d4c831aab3bd496657a36
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp313-cp313-macosx_11_0_arm64.whl

Download URL softqcos-3.15.1-cp313-cp313-macosx_11_0_arm64.whl
Size 1.6 MB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
8954981be82443942526724f34404c0b9fe1c0abb0668ce2e1741a55b9a3539b
BLAKE2b-256 checksum
How to use checksums
4e5049ca68206256c1446cda634dafe10c30a93131366c77cf9dd2941cfca747
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp312-cp312-win_amd64.whl

Download URL softqcos-3.15.1-cp312-cp312-win_amd64.whl
Size 1.3 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
3811f2de27dea74dd350fe730f6574702f4d32c3475f2dc3755c6c67c1f85a89
BLAKE2b-256 checksum
How to use checksums
24c7f09f532df88ffa8a018944c96fc141b34444105c40b8992b9c50f98c956c
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL softqcos-3.15.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.1 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
e2cc45bdbe087ebe9f4d8c72572ffccf88f6103b74eeb4c02e228d8b10204159
BLAKE2b-256 checksum
How to use checksums
184c47e4e9e4cd46c3054e078f0d86e0cd88c363c62ea25ccee02ae8f5581716
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp312-cp312-macosx_11_0_arm64.whl

Download URL softqcos-3.15.1-cp312-cp312-macosx_11_0_arm64.whl
Size 1.5 MB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3325f1076e99a1444cccd9b78742af77a8df74c35398fcb41dfdf937c48266ec
BLAKE2b-256 checksum
How to use checksums
d00cc5cf7260aa8b4f73a4e507d2cc8199c31f030a79839f2383f31e188f6b55
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp311-cp311-win_amd64.whl

Download URL softqcos-3.15.1-cp311-cp311-win_amd64.whl
Size 1.4 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
7b19a83f68b131503f4e4eb45e7ded1e4b998f10bd5ded2e24ce464cbe176366
BLAKE2b-256 checksum
How to use checksums
f861a4e7d16c7af814ffe675366de0c3c7f55927fb2ef071b6a3355547014d91
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL softqcos-3.15.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.8 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
196ccff562fd3eebfb673dcf106a58f8f960e250b6fa86d500ab22d4b7a9115a
BLAKE2b-256 checksum
How to use checksums
a17fa4ac542490c1a3d50df085dd914f92279a424620f1d79f87ccd89b1f06e4
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp311-cp311-macosx_11_0_arm64.whl

Download URL softqcos-3.15.1-cp311-cp311-macosx_11_0_arm64.whl
Size 1.5 MB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
67ddf923d742dd7b20c52c299099b48b1fb8c5fab10056faa33a667e954c09bc
BLAKE2b-256 checksum
How to use checksums
4bdfaea715ad293d3998ca957f2d035984a38800330dbab6e57d7461a8e78c48
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp310-cp310-win_amd64.whl

Download URL softqcos-3.15.1-cp310-cp310-win_amd64.whl
Size 1.3 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
19b3955ad7a5fb817918d27f53aed79ae5d91322ce431059cd206cbe9419978e
BLAKE2b-256 checksum
How to use checksums
1e4418769fdd9b79bba1e989b25ea4a6610275b9e689bc1e26f889e3d6f67cc7
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL softqcos-3.15.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.7 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
47939c31951af18e906adfb463e12a65539158f39ba2ede70b05ecd39cda7b38
BLAKE2b-256 checksum
How to use checksums
a2f7201f4e1aa79f194b553c47fcd3499a1887007612eea9549f0516947e2cd3
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 8, 2026.

Transparency log

Release files / softqcos-3.15.1-cp310-cp310-macosx_11_0_arm64.whl

Download URL softqcos-3.15.1-cp310-cp310-macosx_11_0_arm64.whl
Size 1.5 MB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
d764063b8c377c059e31c89f4ddc094b9c251891ff75d59bc9ae33fa31fa2062
BLAKE2b-256 checksum
How to use checksums
7e0d8daab7ad6eba7dea09684a3cbc5315dc5d41eb67117bbff5fb507b1aa949
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 8, 2026.

Transparency log

Security for softqcos 3.15.1

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

Select from 15 files

Attestation for softqcos-3.15.1-cp314-cp314-win_amd64.whl

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 8, 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