The author of this package has not provided a project description
Metadata
Release files for dsgvhfkjghlj 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 | |
|---|---|---|---|---|
| dsgvhfkjghlj-0.1.0.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dsgvhfkjghlj-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.8 kB
Release files / dsgvhfkjghlj-0.1.0.tar.gz
| Download URL | dsgvhfkjghlj-0.1.0.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e19008a4e9deead3da948fce2750a37aafd9ad9319f49a40191b5186e29931d
|
|
BLAKE2b-256 checksum How to use checksums |
c017dd316b3c02b4012bb9b23242d1f2e91be1602fc24eede67a6829a19a587d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.0
|
Release files / dsgvhfkjghlj-0.1.0-py3-none-any.whl
| Download URL | dsgvhfkjghlj-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
986102bcbfb2738a3f51dfc91c3e428f18614ffd70ecd6db0a4a8ef8eda22a79
|
|
BLAKE2b-256 checksum How to use checksums |
51205005408027e073cb193cdfa8a3f92929881127668dbb1c535a0733cc3ea6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.0
|
Security for dsgvhfkjghlj 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.