Interact with the Lakewatch API.
2 maintainers
Metadata
2 maintainers
Release files for dasl-api 0.1.30
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 | |
|---|---|---|---|---|
| dasl_api-0.1.30.tar.gz | 229.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dasl_api-0.1.30-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 758.5 kB
Release files / dasl_api-0.1.30.tar.gz
| Download URL | dasl_api-0.1.30.tar.gz |
|---|---|
| Size | 229.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c7fa429a1738aa1d871971c71d9eceea43375141fcde7d838bc044d5afec9e4
|
|
BLAKE2b-256 checksum How to use checksums |
f906f398b060ac0464316c86913f34b1bf6a1b382bc71b1ec4e1d5604a50e28d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / dasl_api-0.1.30-py3-none-any.whl
| Download URL | dasl_api-0.1.30-py3-none-any.whl |
|---|---|
| Size | 528.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6be720cc6488b6623e61f73acca22ac98295af9d29e60e9efb83aa97660dd95d
|
|
BLAKE2b-256 checksum How to use checksums |
a6bcea82874a9eec8d6197efa63edd7fd57a925b0af576ae3cb7859454df19dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for dasl-api 0.1.30
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.
