The author of this package has not provided a project description
Metadata
Release files for xserializer 0.0.1
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 | |
|---|---|---|---|---|
| xserializer-0.0.1.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xserializer-0.0.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 4.8 kB
Release files / xserializer-0.0.1.tar.gz
| Download URL | xserializer-0.0.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef432c06bc3b910981e36414db19fb33bb5a289fc595f24e9c5d9a0d5fb0bf58
|
|
BLAKE2b-256 checksum How to use checksums |
99abdc171139145ba8765def62bb5039c64e21ca5e47ceb98e0b3de4974f896d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / xserializer-0.0.1-py2.py3-none-any.whl
| Download URL | xserializer-0.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
c5f5803828e0f92aeffe4a19b415aab4bc4104f8d59c94d613c813b74d52f7de
|
|
BLAKE2b-256 checksum How to use checksums |
92fd6ce0117a15eb98eb91b60ea62350bc9ed53e3fb81ed1ec37cfb5c92132c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for xserializer 0.0.1
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.