2 maintainers
Metadata
2 maintainers
Release files for curious-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 | |
|---|---|---|---|---|
| curious_machine-0.0.1.tar.gz | 3.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| curious_machine-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.5 kB
Release files / curious_machine-0.0.1.tar.gz
| Download URL | curious_machine-0.0.1.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
976334d5c00936f686a7126b794fcb34e19c72c04018dcc530c086773d258522
|
|
BLAKE2b-256 checksum How to use checksums |
f75c87b5320fac25a29795887543d64fa91fa07a9f973e1172af1c96587f6a48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.22
|
Release files / curious_machine-0.0.1-py3-none-any.whl
| Download URL | curious_machine-0.0.1-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1398cae1290542d3faa4fb7882a2b40c71323992cceda88552f680198b701189
|
|
BLAKE2b-256 checksum How to use checksums |
feb4bf1e24f55755fb93e3cceab79ef86b4d360a9b6bba9cbb56b4a2b816fc67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.22
|
Security for curious-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.
