The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tree-diff 0.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 | |
|---|---|---|---|---|
| tree-diff-0.0.1.tar.gz | 3.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tree_diff-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 kB
Release files / tree-diff-0.0.1.tar.gz
| Download URL | tree-diff-0.0.1.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2bfe9355efd501bad8520bd35a6c6c1ec4b0d36b7d8076f621e7b7c8258f7e0
|
|
BLAKE2b-256 checksum How to use checksums |
36e475c82f69d2a15683775c563a6be3def98ebc5f42f855f82a9f1d76bac1a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.7
|
Release files / tree_diff-0.0.1-py3-none-any.whl
| Download URL | tree_diff-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
713e771e9c927096e61c46c1cbfbef05a7a3be4377ff823b5a1cde12c3793f53
|
|
BLAKE2b-256 checksum How to use checksums |
098975afc7dafae2e578dec050ba94fa9807477bfcff5b546b7ae4d670b66e8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.7
|
Security for tree-diff 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.
