2 maintainers
Metadata
2 maintainers
Release files for observing-machine 0.0.1
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 | |
|---|---|---|---|---|
| observing_machine-0.0.1.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| observing_machine-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.6 kB
Release files / observing_machine-0.0.1.tar.gz
| Download URL | observing_machine-0.0.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a4da7c4e4936003c742c392d1e9f0bc85d63535dd3bd1a8f76b77c31fe6bf55
|
|
BLAKE2b-256 checksum How to use checksums |
531bb1ad96e95dbf7c7a8f81ebac3d26eb03870cbc1a9e74f310a51f2ee7373a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / observing_machine-0.0.1-py3-none-any.whl
| Download URL | observing_machine-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
58931f9d51238ae80d40d782f4cc37ad18b9e571fe6cd098f5b72d23a1923056
|
|
BLAKE2b-256 checksum How to use checksums |
23fa16f6776670accb0489fd774c0b9ee1390df691dd21fd5273c76c9a8bd6c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for observing-machine 0.0.1
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.
