The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for abhidrip 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 | |
|---|---|---|---|---|
| abhidrip-0.0.1.tar.gz | 6.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| abhidrip-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.1 kB
Release files / abhidrip-0.0.1.tar.gz
| Download URL | abhidrip-0.0.1.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4236a7e376ddc90b933a5bfe8cc9d781e2009df851e2145574ec45001a8e1ddb
|
|
BLAKE2b-256 checksum How to use checksums |
611baba4c69ba5f303627854d07ccf980dd83d0f459941005ae33d1a8924e8cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / abhidrip-0.0.1-py3-none-any.whl
| Download URL | abhidrip-0.0.1-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2120d4b808dcc9249e8ecaf75b4e8d3939858d15ba0befd0d0d69df5e6008ae4
|
|
BLAKE2b-256 checksum How to use checksums |
fa7b24c94d034a6e501d6bf499f1f92d17eeef4da10a0ca6413c76d19c6f6177
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for abhidrip 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.
