A previous release had provenance metadata, but this release does not. View details.
westquant-bridges
Experimental framework and IR bridges for WestQuant Open.
Support Matrix
| Bridge | Status | Description |
|---|---|---|
| Cirq | EXPERIMENTAL | Circuit import, target-gateset compilation, verification |
| Qibo | EXPERIMENTAL | Circuit import, custom pipeline execution |
| D-Wave Ocean | EXPERIMENTAL | BQM import, embedding/sample controls |
| Amazon Braket | EXPERIMENTAL | Circuit import, OpenQASM Program, local simulation |
| CUDA-Q | EXPERIMENTAL | Program representation, normalized workload profiles, execution hints, cudaq-opt bridge |
| Bloqade | EXPERIMENTAL | Analog program/geometry builder passthrough |
| Microsoft QDK | EXPERIMENTAL | OpenQASM resource estimation |
| OpenQASM 3.1 | STATIC | Dependency-free static representation/metrics |
| QIR | STATIC | Dependency-free LLVM/QIR static representation/metrics |
Note: All SDK-backed bridges are currently EXPERIMENTAL. They have fake/stub tests only, not native SDK tests. Do not rely on them for production use yet.
The four primary frameworks (Qiskit, pytket, PennyLane, Pulser) are SDK_TESTED and available as separate packages:
pip install westquant[qiskit]pip install westquant[pytket]pip install westquant[pennylane]pip install westquant[pulser]
Installation
pip install westquant-bridges
Every external SDK import is lazy so installing WestQuant bridges does not force all quantum SDKs into one Python environment.
For representation-aware CUDA-Q execution planning:
pip install 'westquant-bridges[cudaq]'
The optional extra integrates with westquant-cudaq; it contains no
industry-specific workflow logic.
License
Apache-2.0
1 maintainer
Metadata
1 maintainer
Release files for westquant-bridges 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| westquant_bridges-0.1.1.tar.gz | 18.5 kB | Without provenance | Details for westquant_bridges-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| westquant_bridges-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for westquant_bridges-0.1.1-py3-none-any.whl |
Total release size: 38.1 kB
Release files / westquant_bridges-0.1.1.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | westquant_bridges-0.1.1.tar.gz |
|---|---|
| Size | 18.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ba6c5e93cb38414e94e6eb2e6d9d7dc81ad35575d2cf1b71538f999269f154d
|
|
BLAKE2b-256 checksum How to use checksums |
d57fecc29e415b15c1231542f58a661bd72228138239f8c713da941241bd069f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Release files / westquant_bridges-0.1.1-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | westquant_bridges-0.1.1-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
75b594d7a6dc6e283e0aedf5a525c41abba9cc359a3244f05f9b80fcb9908d31
|
|
BLAKE2b-256 checksum How to use checksums |
3467c631ef2ea92a2f7fa824fae4c0acf3917c13a21601571a90f99e0302343f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Security for westquant-bridges 0.1.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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.1.0a2 2 files With provenance
- Added 0.1.1 2 files Without provenance
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.
