The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for attributionpath 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 | |
|---|---|---|---|---|
| attributionpath-0.0.1.tar.gz | 1.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| attributionpath-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.7 kB
Release files / attributionpath-0.0.1.tar.gz
| Download URL | attributionpath-0.0.1.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76164b28da13ed2df2adb5271a6f00b457acac0acf8a0744182c4e7e27e9e135
|
|
BLAKE2b-256 checksum How to use checksums |
eea4f68e548427412b927f33d8b64dc65341b2707a62dd36625b40b2f94d7b4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.4
|
Release files / attributionpath-0.0.1-py3-none-any.whl
| Download URL | attributionpath-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1cd5e93beab0fb9d7e6f1ff46268dbcce1fe3ac0c495b0f8b7426821eed1e517
|
|
BLAKE2b-256 checksum How to use checksums |
af777afbdd5d4622061f0dc3270c19e23710bf4d9db4241edd679b252e66f4fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.4
|
Security for attributionpath 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.
