sapient-py
Python protobuf bindings and framing helpers for SAPIENT / BSI Flex 335.
This package ships checked-in Python modules generated from the SAPIENT schema source and a small framing helper layer for stream transport.
The generated modules live under sapient_msg, while the framing helpers live
under sapient_py.
Usage
from sapient_msg.bsi_flex_335_v2_0 import sapient_message_pb2
from sapient_py.framing import encode_frame, decode_frame
message = sapient_message_pb2.SapientMessage()
message.node_id = "550e8400-e29b-41d4-a716-446655440000"
frame = encode_frame(message)
decoded = decode_frame(frame, sapient_message_pb2.SapientMessage)
Framing
The framing convention matches the Rust crate:
- 4-byte unsigned little-endian payload length
- followed by the protobuf-encoded
SapientMessagebytes
Licensing
This package is licensed under either MIT or Apache-2.0, at your option.
The SAPIENT .proto schema source from which these bindings were generated is
derived from the DSTL SAPIENT-Proto-Files repository and is separately
attributed to DSTL under Apache License 2.0.
Metadata
Release files for sapient-py 0.1.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 | |
|---|---|---|---|---|
| sapient_py-0.1.0.tar.gz | 33.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sapient_py-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 95.4 kB
Release files / sapient_py-0.1.0.tar.gz
| Download URL | sapient_py-0.1.0.tar.gz |
|---|---|
| Size | 33.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de28a74742c276afceaf9995c56e01075f8966872180990ecff5b9e2b20ed4d2
|
|
BLAKE2b-256 checksum How to use checksums |
12480198bdf3bf8f7f3787921012303a3c7104a912a0867b3f7532b100a4b3dc
|
| 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 Apr 20, 2026.
Transparency logRelease files / sapient_py-0.1.0-py3-none-any.whl
| Download URL | sapient_py-0.1.0-py3-none-any.whl |
|---|---|
| Size | 62.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8f197cda6802948a22df291df29462e08dc5169fea738e50fba06b9aa8aca55a
|
|
BLAKE2b-256 checksum How to use checksums |
5f09053df54cb595f81da444120abafc7092140368a8bba75521f6c03fcf9af5
|
| 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 Apr 20, 2026.
Transparency logSecurity for sapient-py 0.1.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sapient_py-0.1.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 Apr 20, 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.