The author of this package has not provided a project description
Metadata
Release files for feanorTempDir 1.0.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 | |
|---|---|---|---|---|
| feanortempdir-1.0.0.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| feanorTempDir-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.2 kB
Release files / feanortempdir-1.0.0.tar.gz
| Download URL | feanortempdir-1.0.0.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0d4a5e09add8f8262091a4ec90dd408c070ebad8b1070a35c945bc127c6ff3d3
|
|
BLAKE2b-256 checksum How to use checksums |
4c5c89f626f80bb5ea7b2239f3f8ece1cc3b202f93112403bfec2271fa377fed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Release files / feanorTempDir-1.0.0-py3-none-any.whl
| Download URL | feanorTempDir-1.0.0-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7848c66e62c4fc0f6690219d98de391a3d162edf535afd2ee42b8b75b55e342d
|
|
BLAKE2b-256 checksum How to use checksums |
93dd21fb4e9b1ef35b5bc727b796659a9fe965413f4609d0273792210e6b04e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Security for feanorTempDir 1.0.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.