The author of this package has not provided a project description
Metadata
Release files for katalyst-taxonomy 3.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| katalyst_taxonomy-3.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / katalyst_taxonomy-3.4.1-py3-none-any.whl
| Download URL | katalyst_taxonomy-3.4.1-py3-none-any.whl |
|---|---|
| Size | 642.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6eb277cd16c770859e615eb31f44139e12d266f3e7ba7f64664a70c26da40a1e
|
|
BLAKE2b-256 checksum How to use checksums |
4500590e7ace7e0cf94300df541daa0e5379f8ccb9a65cd3a4c7fadcd6cf28db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency logSecurity for katalyst-taxonomy 3.4.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.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for katalyst_taxonomy-3.4.1-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency logA 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.
