The author of this package has not provided a project description
Metadata
Release files for based-metric 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 | |
|---|---|---|---|---|
| based-metric-0.0.3.tar.gz | 1.9 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| based_metric-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.8 MB
Release files / based-metric-0.0.3.tar.gz
| Download URL | based-metric-0.0.3.tar.gz |
|---|---|
| Size | 1.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6159348198e9a731e91b8294fe23a9775598f3a62ce7ff72fcf7987cd3b14095
|
|
BLAKE2b-256 checksum How to use checksums |
bf040fc9a4f3b53f5bfa64d3f1a66099d36f8af46713a25c2dd413f8167e5485
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / based_metric-0.0.3-py3-none-any.whl
| Download URL | based_metric-0.0.3-py3-none-any.whl |
|---|---|
| Size | 2.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26a1d78c1b1502ab8051474b666e86a5deb2d24af532a37d5faac8642e4a0819
|
|
BLAKE2b-256 checksum How to use checksums |
3954361f2356962fc57bd7be35461652605fde03a46ed478ffa4ae9640dea71e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for based-metric 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.