Metadata
Release files for arithematic-niranjan 0.0.3
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 | |
|---|---|---|---|---|
| arithematic_niranjan-0.0.3.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arithematic_niranjan-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.4 kB
Release files / arithematic_niranjan-0.0.3.tar.gz
| Download URL | arithematic_niranjan-0.0.3.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c69c178be7da0c7a5ae0e1bf7a705f7bd07c0216978606a619c3b39afe87dd1
|
|
BLAKE2b-256 checksum How to use checksums |
fa76c41ee65e6f8811a94ed5578c8d1772c3affcd6f2ea9b0e724dd23e371dbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / arithematic_niranjan-0.0.3-py3-none-any.whl
| Download URL | arithematic_niranjan-0.0.3-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5918388e54d43efc284ed3406b232b226be26843015921f20128d30ee3dcbf60
|
|
BLAKE2b-256 checksum How to use checksums |
95c23021622dfe8c1585c100d551f2636de08bf8b7de2ae867c4e6ff30b09ce1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for arithematic-niranjan 0.0.3
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.