The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for dvp-charts 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 | |
|---|---|---|---|---|
| dvp_charts-0.0.1.tar.gz | 3.9 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dvp_charts-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.9 MB
Release files / dvp_charts-0.0.1.tar.gz
| Download URL | dvp_charts-0.0.1.tar.gz |
|---|---|
| Size | 3.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1720f2903316c6722663dde35c3f02828eae4b8eba292e5dd80b15a514b7ba9
|
|
BLAKE2b-256 checksum How to use checksums |
7d473825d9ab9f7884b6593639eaf17caf6b615c6f7526696d0c775ee05d8266
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / dvp_charts-0.0.1-py3-none-any.whl
| Download URL | dvp_charts-0.0.1-py3-none-any.whl |
|---|---|
| Size | 4.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e29a8a654974ad74bd7e6ab94f449cd2116aa2eb43ca0a4e12277f20480e0b93
|
|
BLAKE2b-256 checksum How to use checksums |
04b9f11e07929dde7e196ebecf5952d62ba6d673fb0e3a75fbdd7fdb6d148de5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for dvp-charts 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.
