The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for dougubako 0.0.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 | |
|---|---|---|---|---|
| dougubako-0.0.0.tar.gz | 732 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dougubako-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 kB
Release files / dougubako-0.0.0.tar.gz
| Download URL | dougubako-0.0.0.tar.gz |
|---|---|
| Size | 732 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
215b6a01b752a5467f111abe052b346c4f77025de0b5ccfa0f5f698ef2a8a8ac
|
|
BLAKE2b-256 checksum How to use checksums |
c408406e92b968d8d51d723fe6a8e99b4a555c25961966f427ea7f6d48a4491f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / dougubako-0.0.0-py3-none-any.whl
| Download URL | dougubako-0.0.0-py3-none-any.whl |
|---|---|
| Size | 967 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
176350664e1532d1ad9d9f3fb7812ea74b86d81653998a60c8fbd26fc3605465
|
|
BLAKE2b-256 checksum How to use checksums |
bb8148638166209cf0e548978b86d74fc5eb7146e15c6313804e1b9f19474a2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for dougubako 0.0.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.
