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