This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 3.22 instead.
Reason given by maintainers: Obsolete
dissect
This package serves as a namespace and collection package for all dissect.* related projects. It's only purpose is to secure the dissect namespace, as well as provide an easy way of installing all open-sourced dissect packages.
Currently, it will install the following packages:
- dissect.cstruct
Installation
pip install dissect
1 maintainer
Metadata
1 maintainer
Release files for dissect 1.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 | Actions |
|---|---|---|---|---|
| dissect-1.0.0.tar.gz | 1.2 kB | Without provenance | Details for dissect-1.0.0.tar.gz |
Release files / dissect-1.0.0.tar.gz
| Download URL | dissect-1.0.0.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5786f946f59181e97f0d09519f1e2ab15c850945d5902b8c593b4f36a0d866d
|
|
BLAKE2b-256 checksum How to use checksums |
375b4e927c5acde33d9a3fd40cb1d3dca2409037e178e52b691b31d8e1a2a196
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.1.0 requests-toolbelt/0.9.1 tqdm/4.42.1 CPython/3.6.6
|
Security for dissect 1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
