The author of this package has not provided a project description
Metadata
Release files for rocket-aymen 1.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 | |
|---|---|---|---|---|
| rocket_aymen-1.0.0.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rocket_aymen-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.7 kB
Release files / rocket_aymen-1.0.0.tar.gz
| Download URL | rocket_aymen-1.0.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5eb4ccb622de45872ae56b045312f632672f53d2354e4e9f35816f5ebfbd2786
|
|
BLAKE2b-256 checksum How to use checksums |
bf30c08487a254d0b265cfd8cc9eef2dcb6593a8a93f444f5856f13a61cb631c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / rocket_aymen-1.0.0-py3-none-any.whl
| Download URL | rocket_aymen-1.0.0-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09afb64919c743d0e983af74947b15b821c5af3731a20aa10d3621bdb90100e5
|
|
BLAKE2b-256 checksum How to use checksums |
1372f9494d6509ff36b47cb15f003f33a8cde4a1b9c79e6c113db1a2626a51f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for rocket-aymen 1.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.