Metadata
Release files for smartphone_robot_flatbuffers 0.0.2
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 | |
|---|---|---|---|---|
| smartphone_robot_flatbuffers-0.0.2.tar.gz | 12.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| smartphone_robot_flatbuffers-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.9 kB
Release files / smartphone_robot_flatbuffers-0.0.2.tar.gz
| Download URL | smartphone_robot_flatbuffers-0.0.2.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eeb10f38a526210ddc700060825254470723ea5f7c0de04af9b7bfe45f31aa78
|
|
BLAKE2b-256 checksum How to use checksums |
58afe639d9643f4f4b38f8f52a623a014dac7c40a09037e253da129d0d397d0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.27.0
|
Release files / smartphone_robot_flatbuffers-0.0.2-py3-none-any.whl
| Download URL | smartphone_robot_flatbuffers-0.0.2-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01bcc1767767b72ef378e77bd9aab38b0dccd7a7353b0909eacb9f295cb58622
|
|
BLAKE2b-256 checksum How to use checksums |
af6b10aa601cafc0e69c52e83d32bce2e780b7657af82eebecc4fcc008578f06
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.27.0
|
Security for smartphone_robot_flatbuffers 0.0.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.