Metadata
Release files for battery_management 0.2.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 | |
|---|---|---|---|---|
| battery_management-0.2.0.tar.gz | 38.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| battery_management-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.3 kB
Release files / battery_management-0.2.0.tar.gz
| Download URL | battery_management-0.2.0.tar.gz |
|---|---|
| Size | 38.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4cc0395aff10075eeb4d112dd48b245b4dcda4fd09b6388af626847421b1828
|
|
BLAKE2b-256 checksum How to use checksums |
6158f5390a7d634b6f35b38ab9f0dabc4751fbd4ffd592f6d6350b893a877682
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.11.9 Linux/6.5.0-1025-azure
|
Release files / battery_management-0.2.0-py3-none-any.whl
| Download URL | battery_management-0.2.0-py3-none-any.whl |
|---|---|
| Size | 49.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2077b8f254743f5e39517887a8717393fcb2d7ba1563b53cc54a12bbc54d9147
|
|
BLAKE2b-256 checksum How to use checksums |
12f07b0e41cf16557bd6e41cf4104766b708c82b51a41fa63687563cfde4ffe5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.11.9 Linux/6.5.0-1025-azure
|
Security for battery_management 0.2.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.