机械蜘蛛的依赖库
Metadata
Release files for Dmaker 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dmaker-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
| Dmaker-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.0 kB
Release files / dmaker-0.0.1-py3-none-any.whl
| Download URL | dmaker-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
85219907772c98c5bf72e63bd41ea85af7e69a69a44ebf2f7dfec9bfc83b760c
|
|
BLAKE2b-256 checksum How to use checksums |
c9bca1f98b0131d948b46b138e57d40947f6233e7d66d4701d6a831189165d14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.14.0 pkginfo/1.5.0.1 requests/2.19.1 setuptools/39.1.0 requests-toolbelt/0.9.1 tqdm/4.25.0 CPython/3.6.5
|
Release files / Dmaker-0.0.1-py3-none-any.whl
| Download URL | Dmaker-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e086791284b7fe3b38a5a6f63f0f3dd928ba636a77191fd57cacf908f81373c
|
|
BLAKE2b-256 checksum How to use checksums |
f22d9ba47e97baee47ac4110da317fcb1da18c0f1a029f7f2e4b5fcd532def33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.14.0 pkginfo/1.5.0.1 requests/2.19.1 setuptools/39.1.0 requests-toolbelt/0.9.1 tqdm/4.25.0 CPython/3.6.5
|
Security for Dmaker 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.