The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for ab-methods 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 | |
|---|---|---|---|---|
| ab_methods-0.1.0.tar.gz | 11.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ab_methods-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.8 kB
Release files / ab_methods-0.1.0.tar.gz
| Download URL | ab_methods-0.1.0.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b660c9c4b2dadd86e246c717cc3870b09528b8e2ec09f241023d5a13412361dd
|
|
BLAKE2b-256 checksum How to use checksums |
d3beb47e08a0e36b6a9a2542060399d78ceafa2945e893c6529e3220eea16be7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.2
|
Release files / ab_methods-0.1.0-py3-none-any.whl
| Download URL | ab_methods-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
312b1516c09aebf1ea15b20aefabf8a6a8731231d40b1132c9e444fb0bfe0e0b
|
|
BLAKE2b-256 checksum How to use checksums |
55c8329fc25a9467921c3b4e278631e38b12c03816cc153d346f751673db07a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.2
|
Security for ab-methods 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.
