My first Python package with a slightly longer description
1 maintainer
Metadata
1 maintainer
Release files for base-folder 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 | |
|---|---|---|---|---|
| base-folder-0.0.1.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| base_folder-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.0 kB
Release files / base-folder-0.0.1.tar.gz
| Download URL | base-folder-0.0.1.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9cb83c2021334ef62c5923fdd67f8057d5150c301696318da3b6724f6eae25f4
|
|
BLAKE2b-256 checksum How to use checksums |
d94958f2d81e1c649397925d5f58a3ab35f5877bd01ad857310a794c7b469733
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / base_folder-0.0.1-py3-none-any.whl
| Download URL | base_folder-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02d36f983ce07d47c641efadaddf95b1166a82f0fc5a585134ad71018ff955e2
|
|
BLAKE2b-256 checksum How to use checksums |
a711933e329dcc9e2b87e3ec187be476aa6bba08dccf967c352bb018b4607d9d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for base-folder 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.
