机械蜘蛛的依赖库
Metadata
Release files for DDmaker 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 |
|---|---|---|---|---|
| ddmaker-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
| DDmaker-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.0 kB
Release files / ddmaker-0.0.1-py3-none-any.whl
| Download URL | ddmaker-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a4cd05cec23539358fa64d60771082daa42627f01fed2ddb42d4f195cbf70183
|
|
BLAKE2b-256 checksum How to use checksums |
07599c39214c90d6de8a4b9237e3d41f3a99c7830f34f839c8eeb1477e70e139
|
| 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 / DDmaker-0.0.1-py3-none-any.whl
| Download URL | DDmaker-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8362ae8c98a1f612df75e8b6b98aa6f034181aa23d3787183aa3adfa69c56b1
|
|
BLAKE2b-256 checksum How to use checksums |
3a9b98a1fac9bd86073a2d96eaaf7f76723e2d970a95be3f189758e833e88645
|
| 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 DDmaker 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.