chase-cps
Python interface to CHASE (Contract-based Heterogeneous Analysis and Systems Exploration), a framework for requirement capture, formalization, and validation of cyber-physical systems with assume-guarantee contracts.
The package contains the CHASE core library (contract representation and algebra) and a common interface to model checkers and synthesis tools.
from chase_cps import Contract, refines
spec = Contract.from_strings(inputs=["req"], outputs=["grant"],
assumptions=["G F !req"],
guarantees=["G (req -> F grant)"], name="Spec")
impl = Contract.from_strings(inputs=["req"], outputs=["grant"],
guarantees=["G (req -> X grant)"], name="Impl")
result = refines(impl, spec)
print(result.status) # valid, or invalid with a counterexample trace
The operations have the names of the commands of logics_tool, in three
layers:
- Contracts and their algebra (
chase_cps.contract). A contractchas the methodscompose,conjoin,disjoin,merge,divide(quotient),separate,imply,coimply,invert(reciprocal),assume,ensure,saturate, andsimplify, which return new contracts. They hold for any assume-guarantee contracts. - Checks (
chase_cps.checks,chase_cps.logic). The checks on contracts arerefines,verify(A & G satisfiable, which impliesis_compatibleandis_consistent),is_implementation(a component satisfies the contract),is_environment(an environment satisfies the assumptions),is_receptive, andremove_redundant; the components and environments can be LTL formulas or state machines (Model: SMV, JSON, or a synthesized controller). They reduce to queries on formulas:implies(validity),is_satisfiable(satisfiability of a formula), andunsat_core. Acontextgives formulas that every behavior satisfies. - GR(1) synthesis (
chase_cps.gr1):is_realizable,synthesize,unrealizable_core,is_well_separated, andis_vacuous(vacuity in synthesis), for contracts in the GR(1) fragment of LTL.remove_redundant(c, synth=True)drops the terms that are redundant in the GR(1) game, before synthesis.
All the names are also in chase_cps. load_spec and parse_spec read the
contracts of a specification written in the logics language of CHASE, and
to_spec writes one. parse_sva reads the assume property and assert property statements of SystemVerilog as a contract, and to_sva writes a
contract as a checker module. to_gr1(c, tool="slugs" | "gr1c") writes a
GR(1) contract for a solver you run yourself, to_smv and to_smt the
checks of a contract for nuXmv, NuSMV, z3, or cvc5, to_c the check of a C
function for ESBMC or CBMC, and load_dsl reads a problem
written in the domain-specific language of CHASE. The variables are
Booleans, integer ranges,
reals, and words ("word[8]", "signed word[8]"); past(x, n) is the
value of x n steps before. nuXmv runs IC3 and BDDs at the same time; the
option engine chooses one. The details are in
docs/usage.md.
Installation
$> pip install chase-cps
Wheels are available for Python 3.10 to 3.15 on Linux (x86_64 and aarch64, glibc 2.28 or later) and macOS 11 or later (arm64 and x86_64). Windows is not supported: use WSL or the CHASE Docker image.
Requirements
The package contains the CHASE library. The checks call external tools, which are not installed with the package:
- nuXmv for the checks (layer 2) and
remove_redundant. nuXmv is free for academic and non-commercial use. - slugs for the other analyses of GR(1) synthesis (layer 3).
The command chase-cps install downloads nuXmv from its site, and builds
slugs from its sources, into ~/.chase:
$> chase-cps install nuxmv --accept-license # Linux x86_64, macOS arm64
$> chase-cps install slugs # needs a C++ compiler, make, and Boost
On macOS, nuXmv needs the libraries of Homebrew (brew install libxml2 gmp libedit). On Linux it needs libxml2 and libedit2, and the C++ library of
GCC 13 or later (Ubuntu 24.04, Debian 13, Fedora 39, or newer);
chase-cps install says what is missing.
The tools can also be installed by hand: they are looked up in the PATH
and in ~/.chase/bin, or given with the environment variables CHASE_NUXMV
and CHASE_SLUGS. The command
$> chase-cps doctor
shows the tools found and how to install the missing ones.
Where nuXmv cannot be used (e.g. for commercial purposes), the checks run
with NuSMV (LGPL) instead: chase-cps install nusmv installs it on
Linux x86_64, or set CHASE_NUSMV.
Diagrams
chase_cps.viz draws contracts, components, and systems as a web page:
a box inside another is checked against it, a quotient is a dashed box, a
model opens on its states, and the results of the checks are tags on the
boxes, with their cores highlighted.
from chase_cps import Contract, refines, viz
spec = Contract.from_strings(inputs=["req"], outputs=["grant"], assumptions=["G F !req"],
guarantees=["G (req -> F grant)"], name="Spec")
impl = Contract.from_strings(inputs=["req"], outputs=["grant"],
guarantees=["G (req -> X grant)"], name="Impl")
d = viz.diagram(spec, refines=[(impl, spec, refines(impl, spec))], open=[spec])
viz.save(d, "plan.html") # viz.show(d) opens it in a browser
Command line
chase-cps check checks the contracts of a specification written in the
logics language of CHASE, or of a JSON file, and prints the counterexamples:
$> chase-cps check specs.ltl # verify every contract
$> chase-cps check specs.ltl --refines Joint1+Joint2 Joints # composition refines Joints
$> chase-cps check specs.ltl --realizable Joint1 --json
$> chase-cps check specs.ltl --implementation joint1.smv Joint1 --receptive joint1.smv Joint1
The exit status is 0 when every check passes, and 1 when a check fails.
chase-cps view specs.ltl --check --realizable writes the diagram of a
specification, and --serve draws it again whenever the file changes.
The source code and the installation instructions are in the chase repository.
1 maintainer
Metadata
1 maintainer
Release files for chase-cps 0.6.4
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 |
|---|---|---|---|---|
| chase_cps-0.6.4.tar.gz | 6.1 MB | With provenance | Details for chase_cps-0.6.4.tar.gz |
Built distributions (wheels)
Total release size: 61.8 MB
Release files / chase_cps-0.6.4.tar.gz
| Download URL | chase_cps-0.6.4.tar.gz |
|---|---|
| Size | 6.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86ef08e6431ed2257a10aed70f9f5103169dd5894b3492530326a492e356eb01
|
|
BLAKE2b-256 checksum How to use checksums |
de67a81cc04b67848661505bc0263f2bad5eaf1e3355dfac0c60b56d2bdb01b1
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp315-cp315-manylinux_2_28_x86_64.whl
| Download URL | chase_cps-0.6.4-cp315-cp315-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.15 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
633c1d17dfee17829d535e1384a45677b3d2d9da5cf673a7485763dfc7e32493
|
|
BLAKE2b-256 checksum How to use checksums |
414a766ae1fff690dac73212b8338390d7086ae7813b43f9bdeeebe610ef50aa
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp315-cp315-manylinux_2_28_aarch64.whl
| Download URL | chase_cps-0.6.4-cp315-cp315-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.15 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
ed3c76f986c4147e0ff8c098e9db63ec35b582646e2104f12b51201a097093fc
|
|
BLAKE2b-256 checksum How to use checksums |
2d83690bd378b1464b76919fb748655436deeb7f3e37f830fc4bd9f172c016df
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp315-cp315-macosx_11_0_x86_64.whl
| Download URL | chase_cps-0.6.4-cp315-cp315-macosx_11_0_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.15 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
4da3718b78ea955ed6e5d8db58b0e65399be93f2c32fb6fcf289453af61ea39e
|
|
BLAKE2b-256 checksum How to use checksums |
34ce775c56baf0b65b9e81fd7796af5e223aa57bb4f1ab9d51d1d11401dd589b
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp315-cp315-macosx_11_0_arm64.whl
| Download URL | chase_cps-0.6.4-cp315-cp315-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.15 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
4cf455cc7aa91837a1a95693fe005071837972813ea6d2ee060db0feff94b694
|
|
BLAKE2b-256 checksum How to use checksums |
466c385d3f92f9054b4f76b744a274027610a2ca4a002a8f67bd7047c10c0db7
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp314-cp314-manylinux_2_28_x86_64.whl
| Download URL | chase_cps-0.6.4-cp314-cp314-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.14 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
46133c017a245f0b5ab6283d354ea7443286d36b2004f1ced78b1409cb3312ed
|
|
BLAKE2b-256 checksum How to use checksums |
8e84951afec3a4d83be90a84ed735c6abc8459b77514f25eb7b6b876a0610e51
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp314-cp314-manylinux_2_28_aarch64.whl
| Download URL | chase_cps-0.6.4-cp314-cp314-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.14 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
adc521c4a262e5bff4e3c9bb30e34d8d08aabb2f4a8badf69da34b41865cbace
|
|
BLAKE2b-256 checksum How to use checksums |
0cb187c25918deec73a5b017f7e430da5e51b0ee3cc3e48ce3438dff73453920
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp314-cp314-macosx_11_0_x86_64.whl
| Download URL | chase_cps-0.6.4-cp314-cp314-macosx_11_0_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.14 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
75d01cce04816721d5158bb15ef3d5829bb13107ced5b79b7751b0fa986a79e2
|
|
BLAKE2b-256 checksum How to use checksums |
91ac6e47d59fdbe8587f9ade150ff6bd65bc5a8902a42c400f02aabe928042f4
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | chase_cps-0.6.4-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
eba36b362dd6b1ae691b4b3eed5f18c5097ce25ab246f8a55f825887a562ade7
|
|
BLAKE2b-256 checksum How to use checksums |
097b92ddf50797eec554afaf9cba0cfd98f4891e912091b166e90a95808922d1
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp313-cp313-manylinux_2_28_x86_64.whl
| Download URL | chase_cps-0.6.4-cp313-cp313-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ed3eb5b7f990d12741b29c9eccf55bf79dd6612c316e9c2f26a743cd04462746
|
|
BLAKE2b-256 checksum How to use checksums |
db3b227ad442e3019ace9be3fc97b03eac710a64dc68ad744a93b9190e2af637
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp313-cp313-manylinux_2_28_aarch64.whl
| Download URL | chase_cps-0.6.4-cp313-cp313-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
801d7421985a26507446554bdb0b447c501eef3775885202022cac96f1874f78
|
|
BLAKE2b-256 checksum How to use checksums |
1c39bc475a540aec98a1862568f8c2946b110c17697b794de880686e258fc3bb
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp313-cp313-macosx_11_0_x86_64.whl
| Download URL | chase_cps-0.6.4-cp313-cp313-macosx_11_0_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.13 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
52c0bae43472763ce2357e8ba5fb09c4d3426cb24d8751a84eb0ac7d762ed0d3
|
|
BLAKE2b-256 checksum How to use checksums |
dab534883e768be198309e367009a2288ebefed2a9d82cd1edabbbda4f00f477
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | chase_cps-0.6.4-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3e419664eaa2bb22c311c9153e4f1aa39c60e41e302c77396c5654a2ef5d3822
|
|
BLAKE2b-256 checksum How to use checksums |
06411da0b88ae5c596ae94ce91b236537097233a8b8db75d7ed888842f7b537f
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp312-cp312-manylinux_2_28_x86_64.whl
| Download URL | chase_cps-0.6.4-cp312-cp312-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
4d9ea41ac6c5cf911db18fa7957b1302519719b971229b310d60f678777e9f6e
|
|
BLAKE2b-256 checksum How to use checksums |
693eb70cb2167ff2530bb1322e54495ed4c14e4ef2fc68b3c95c3362a70cb663
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp312-cp312-manylinux_2_28_aarch64.whl
| Download URL | chase_cps-0.6.4-cp312-cp312-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
234ae563a0f05488c3bc684030810196c3f53097e568a90c94071c6acee1336a
|
|
BLAKE2b-256 checksum How to use checksums |
3e8cbdbf715da672bf47b3cd714d005ba38bbe837df2178b709e5cb1456fda99
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp312-cp312-macosx_11_0_x86_64.whl
| Download URL | chase_cps-0.6.4-cp312-cp312-macosx_11_0_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.12 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
1763cad4814888089088b0eb78e249dd0b7135fb6db7c4574d64eec0302da9b9
|
|
BLAKE2b-256 checksum How to use checksums |
5cf4a17f93ded09f148f63be2539dca1f2ea493214438234453a7ea379c83f5b
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | chase_cps-0.6.4-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2267ccac7aec773f01b9379dc592abb3d610fc89a77d678edff3bec13130d93e
|
|
BLAKE2b-256 checksum How to use checksums |
a089bbbf00ea3c9dfa380d3ecb8d68e3ab3637e1f253070c875e2b783663fa6d
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp311-cp311-manylinux_2_28_x86_64.whl
| Download URL | chase_cps-0.6.4-cp311-cp311-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
95949166b7af8ee88865c0ea413e90d09303e496cfa3d456b1dad9ebe0af09c9
|
|
BLAKE2b-256 checksum How to use checksums |
f01ed2ac7feada5b788c97af1a9d9a01e348ff665901317c91df394b0b70e3af
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp311-cp311-manylinux_2_28_aarch64.whl
| Download URL | chase_cps-0.6.4-cp311-cp311-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
96be57ec4dcc614a1fee599742eabed69a7aaafe0305c6373ce4eb27b85e74b3
|
|
BLAKE2b-256 checksum How to use checksums |
8d3feb3c78117d999d2b0f907242732655bc5a662788b3f4b64a84cd37613ae1
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp311-cp311-macosx_11_0_x86_64.whl
| Download URL | chase_cps-0.6.4-cp311-cp311-macosx_11_0_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.11 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
a1ce2fa325386fe3bd058d8d153979185f4fc045f17e63ea9e878c2515580fa0
|
|
BLAKE2b-256 checksum How to use checksums |
482a6a9a4276da89f528b6119160617ccb44608ea779b5bc4fcaace993195331
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | chase_cps-0.6.4-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a3e0dc00980f05a3efeccbcaf3c264ad3eec65f11c121892227c73206296f2a3
|
|
BLAKE2b-256 checksum How to use checksums |
fe6fd532eb708a97310e482c4d328de2d36dc3d17f736eee590a50b6a4369bf3
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp310-cp310-manylinux_2_28_x86_64.whl
| Download URL | chase_cps-0.6.4-cp310-cp310-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
31d81459611ed738102f9150ae0fa024088c2193416ebee20e1dd1b3d3d6937e
|
|
BLAKE2b-256 checksum How to use checksums |
db5d648b498c8ddfbbb529993419111107069ec015db7dba949b1f5033b1b5a7
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp310-cp310-manylinux_2_28_aarch64.whl
| Download URL | chase_cps-0.6.4-cp310-cp310-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
e43fbf8306c1a37e6a3b74b2a7283a5e122fd0548840f226ca7ba150dadcbb8b
|
|
BLAKE2b-256 checksum How to use checksums |
f7a2c6477df77340175fdbb58871162ed70dbe4a05af3aec5e0de8a283c415e0
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp310-cp310-macosx_11_0_x86_64.whl
| Download URL | chase_cps-0.6.4-cp310-cp310-macosx_11_0_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.10 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
82c6b31f3aa9b805e96d1964b32a7775be4b3c53c56d8b466d343066faba502a
|
|
BLAKE2b-256 checksum How to use checksums |
829477b0b409d01b9137cf902f9584b2435471852b74ebc9f6b8e2b839042b3e
|
| 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 1, 2026.
Transparency logRelease files / chase_cps-0.6.4-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | chase_cps-0.6.4-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a59b0294c643bf7e894d30650630a7c54c5568e82077d0c3af41dace0411babc
|
|
BLAKE2b-256 checksum How to use checksums |
4f1e2e6e5520b66b41e1898c1d9e2e82df26aa9eb62c145602dd1b7022dc36fe
|
| 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 1, 2026.
Transparency logSecurity for chase-cps 0.6.4
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 25 files in this release have been uploaded with provenance metadata.
Attestation for chase_cps-0.6.4.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 1, 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.
