capus → capusqa
This package has been renamed to capusqa.
capus is now a thin compatibility shim that installs capusqa for you. Please
switch to the new name:
uv tool install 'capusqa[browser]'
capusqa setup
Installing capus (or capus[browser]) keeps working — it pulls in the latest
capusqa and the capus command still runs CapusQA — but new features and docs
live under capusqa.
1 maintainer
Metadata
1 maintainer
Release files for capus 2.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| capus-2.3.0.tar.gz | 1.3 kB | With provenance | Details for capus-2.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| capus-2.3.0-py3-none-any.whl | Python 3 | none | any | Details for capus-2.3.0-py3-none-any.whl |
Total release size: 2.8 kB
Release files / capus-2.3.0.tar.gz
| Download URL | capus-2.3.0.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
302ff3e0537c1c2c361fb1eddca22279b58dc5a5a20416cfa49c2270c53ec734
|
|
BLAKE2b-256 checksum How to use checksums |
46929a39ab32eaab5f1561811657bcca115e6c3cbec8d51e6d137363618f773a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 22, 2026.
Transparency logRelease files / capus-2.3.0-py3-none-any.whl
| Download URL | capus-2.3.0-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3717a6f8a7e2c90043adef5df7bfa40fd344ee9bf886a493ff76e40f8a51f45d
|
|
BLAKE2b-256 checksum How to use checksums |
51234b4d1d262e3e6e1c2a87af4342cf6fad9a333f7fd035b00110eb8ed0c4bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 22, 2026.
Transparency logSecurity for capus 2.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
Both files in this release have been uploaded with provenance metadata.
Attestation for capus-2.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 Jun 22, 2026.
Transparency logA 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.
