sayfirst-boundary
The in-process boundary. A governed program opens Boundary.request(...) around
an effect; the decision lands before the body runs, or the body does not run.
This distribution holds no policy and decides nothing. It asks the control plane
over a socket whose peer it verified, caches an allow as a grant for exactly
the question it answers, and stops honouring that grant the moment any of four
things happens: the connection carrying it ends, its lifetime runs out, the
policy version it was issued under changes, or the control plane goes silent for
a lifetime. Built with hold_grants=False, it holds nothing and asks for every
act — what a verifier needs, whose proof is one recorded decision for each
effect, while a grant hit records none.
It publishes no exit codes. Outcomes leave as exceptions, and a caller that runs a process decides what to exit with.
Metadata
Release files for sayfirst-boundary 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_boundary-0.3.3.tar.gz | 28.6 kB | With provenance | Details for sayfirst_boundary-0.3.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sayfirst_boundary-0.3.3-py3-none-any.whl | Python 3 | none | any | Details for sayfirst_boundary-0.3.3-py3-none-any.whl |
Total release size: 48.9 kB
Release files / sayfirst_boundary-0.3.3.tar.gz
| Download URL | sayfirst_boundary-0.3.3.tar.gz |
|---|---|
| Size | 28.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5747d98e15e70633b464c89c5363c942e438aa7aa9c702d3c69fcffb460650f
|
|
BLAKE2b-256 checksum How to use checksums |
64e02b5166ecca26c971262d8941b443f5be5e445e3ea060da800492702a531c
|
| 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_boundary-0.3.3-py3-none-any.whl
| Download URL | sayfirst_boundary-0.3.3-py3-none-any.whl |
|---|---|
| Size | 20.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f50ddc6ebf1da2797759901543972566bc48b03bcfb5fff2e4748a6660fdb578
|
|
BLAKE2b-256 checksum How to use checksums |
fa530d0f812b236949d6abe53ce85c7362ab145aefb5ca981e67c970c9f942bb
|
| 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-boundary 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_boundary-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.