The author of this package has not provided a project description
Metadata
Release files for rocket-saja 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 | |
|---|---|---|---|---|
| rocket_saja-0.1.0.tar.gz | 2.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rocket_saja-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.9 kB
Release files / rocket_saja-0.1.0.tar.gz
| Download URL | rocket_saja-0.1.0.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a1ddfef2595b0937c972cb39f39f8dd002e8f2ba6e48a5fa3b1577c0521ba4b
|
|
BLAKE2b-256 checksum How to use checksums |
43c04833cffd447dd42fdc8df6336c1de6ff9f2c7dd64bd2d36999a2fbaa9774
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Release files / rocket_saja-0.1.0-py3-none-any.whl
| Download URL | rocket_saja-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac5c466d3705836eec0317f22f4de875813e7add5bd7ee939166dff80b929d08
|
|
BLAKE2b-256 checksum How to use checksums |
01b00cab7ecf257b57f9d45093e6e166137e67f495664c7d3e069671480f0f5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Security for rocket-saja 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.