The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for autools-isee 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 | |
|---|---|---|---|---|
| autools_isee-0.1.0.tar.gz | 3.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autools_isee-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.1 kB
Release files / autools_isee-0.1.0.tar.gz
| Download URL | autools_isee-0.1.0.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9894c13cab8d3348f7258c7dd5ed623f1f9dbff4ac1f8455b1af4e2e03b4ed0
|
|
BLAKE2b-256 checksum How to use checksums |
70638980e5dac05d8ad2603867fffce640802c328f944493ed8c48f94bbf0ea5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.16
|
Release files / autools_isee-0.1.0-py3-none-any.whl
| Download URL | autools_isee-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e941fa51a5642018bc127b351532125fe8f359637851f678a34261bc672ceaa
|
|
BLAKE2b-256 checksum How to use checksums |
3bc79950e840844cb2b876b521e573b5f2679f88a3cd956a8f3d30de4bbc4638
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.16
|
Security for autools-isee 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.
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.
