1 maintainer
Metadata
1 maintainer
Release files for sttjenerator 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 | |
|---|---|---|---|---|
| sttjenerator-0.1.0.tar.gz | 4.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sttjenerator-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.0 kB
Release files / sttjenerator-0.1.0.tar.gz
| Download URL | sttjenerator-0.1.0.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0303b515134d2193e3811ec419d5cb10322a94eb94c937eb6e0e047f5b10f9e8
|
|
BLAKE2b-256 checksum How to use checksums |
a954228b503f0a40674bd6ba9035a20f994e60cebbd852dbe47e2f38d93fb520
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.3.2 CPython/3.12.3 Linux/6.17.0-35-generic
|
Release files / sttjenerator-0.1.0-py3-none-any.whl
| Download URL | sttjenerator-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
85deb2996a4ac69550bb4dcf4b3fc1747d8e359cd9234f9ad90e55cccf4653bc
|
|
BLAKE2b-256 checksum How to use checksums |
438d8a6d01dfb8ccba8ffc9392e113c9bd237edbde2f5e1b08140cd048ca450a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.3.2 CPython/3.12.3 Linux/6.17.0-35-generic
|
Security for sttjenerator 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.
