sayfirst-contract-stub
A scriptable, non-authoritative fake of the control plane contract.
It exists so that a client can be exercised without a daemon: it answers the routes the binding
declares, from answers a test writes into it, and it decides nothing. Nothing it returns is a
decision of this control plane, and no deployment installs it to obtain one — it is installed by
the stub extra of sayfirst-contract and it belongs in a test environment.
What it is good for: proving that a client renders an answer as it was given, that it exits on the
code it published, and that it refuses a peer it did not verify. What it is not good for: any
claim about what the control plane would decide. For that, the conformance replay
(sayfirst-conformance) drives a real server against the published scenarios.
Licensed under the Apache License 2.0; see LICENSE and NOTICE in the distribution.
Metadata
Release files for sayfirst-contract-stub 0.3.3
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 |
|---|---|---|---|---|
| sayfirst_contract_stub-0.3.3.tar.gz | 35.8 kB | With provenance | Details for sayfirst_contract_stub-0.3.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sayfirst_contract_stub-0.3.3-py3-none-any.whl | Python 3 | none | any | Details for sayfirst_contract_stub-0.3.3-py3-none-any.whl |
Total release size: 58.2 kB
Release files / sayfirst_contract_stub-0.3.3.tar.gz
| Download URL | sayfirst_contract_stub-0.3.3.tar.gz |
|---|---|
| Size | 35.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e23faa89252feef255a22582abf2f65d298f48fd5d082d38c0448554f6c86a9
|
|
BLAKE2b-256 checksum How to use checksums |
dbe02951fbe933d7f3ab27ae1adb90971458cd3f819835f03fa3693b205ddc9f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 1, 2026.
Transparency logRelease files / sayfirst_contract_stub-0.3.3-py3-none-any.whl
| Download URL | sayfirst_contract_stub-0.3.3-py3-none-any.whl |
|---|---|
| Size | 22.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
24aabd02d3f1aaeea5611b0ea145194d6e6c2c6c6b7c9bab674a7ed5abe4163d
|
|
BLAKE2b-256 checksum How to use checksums |
1c665ddf639dda8eee1ace57d51731e30e6a08cf2ef1b8c9dd7d844e692dc6a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 1, 2026.
Transparency logSecurity for sayfirst-contract-stub 0.3.3
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 sayfirst_contract_stub-0.3.3.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 Oct 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.