The author of this package has not provided a project description
Metadata
Release files for particle45 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 | |
|---|---|---|---|---|
| particle45-0.1.0.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| particle45-0.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 3.5 kB
Release files / particle45-0.1.0.tar.gz
| Download URL | particle45-0.1.0.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25924e23ae6c8d08525deeafb548cc936a1127f1e0aa5dedb12bedbcddf5ee16
|
|
BLAKE2b-256 checksum How to use checksums |
730a580f78748b190335a7aeb9f89a7aa12e9a3ecbd8b85efcbd9aa122a9ee14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.28.1
|
Release files / particle45-0.1.0-py2.py3-none-any.whl
| Download URL | particle45-0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 2.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7d2fc7fff252825a9b575bea8c1e3c7463b6fc574aaa4aad67cc17b7ca39ba46
|
|
BLAKE2b-256 checksum How to use checksums |
a1e524ddaacc288c238974997ebdd0efca2289b43285126c7afc7df8721094de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.28.1
|
Security for particle45 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.