2 maintainers
Metadata
2 maintainers
Release files for wpushnotif-parser 0.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 | |
|---|---|---|---|---|
| wpushnotif_parser-0.0.0.tar.gz | 750 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wpushnotif_parser-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.2 kB
Release files / wpushnotif_parser-0.0.0.tar.gz
| Download URL | wpushnotif_parser-0.0.0.tar.gz |
|---|---|
| Size | 750 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed92112d60027294a611819f27ae52881a867d6bce1e22f9d16085c97b405b8b
|
|
BLAKE2b-256 checksum How to use checksums |
4f9f7fd6ab72f6e0e61285b0125591528c086b4ccba307039ed3e54dd72f6a96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / wpushnotif_parser-0.0.0-py3-none-any.whl
| Download URL | wpushnotif_parser-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fee2ad1d87667b0874c47a1a276e9369cd9ee754ab674e4fb55a349fbf4df2f2
|
|
BLAKE2b-256 checksum How to use checksums |
985958efec404b83dfd2d4148b6c7bd54166b6f229cad3524d1ef0c1cf9aacb5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for wpushnotif-parser 0.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.
