The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pynetrees 1.0.1
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 | |
|---|---|---|---|---|
| pynetrees-1.0.1.tar.gz | 9.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pynetrees-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.5 kB
Release files / pynetrees-1.0.1.tar.gz
| Download URL | pynetrees-1.0.1.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07e62f0a802d395999376c017da21265d5839d32f87f6a1ad5f0162f33d971d0
|
|
BLAKE2b-256 checksum How to use checksums |
3852f3bca30bb946e5e24568a026ade354ed3eee566b776625dc00175012170e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.11 CPython/3.6.7 Linux/4.15.0-45-generic
|
Release files / pynetrees-1.0.1-py3-none-any.whl
| Download URL | pynetrees-1.0.1-py3-none-any.whl |
|---|---|
| Size | 35.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2f2c740abd39a4daa3946db377fba6875a8de82286d928dfaf73a78cf176525
|
|
BLAKE2b-256 checksum How to use checksums |
2eafb10f1447190352afd775b0d1fb85b4a68c09bb7acd05b0852e3907cc0f90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.11 CPython/3.6.7 Linux/4.15.0-45-generic
|
Security for pynetrees 1.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.
