The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for ml-shap-xai 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 | |
|---|---|---|---|---|
| ml_shap_xai-0.1.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ml_shap_xai-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.7 kB
Release files / ml_shap_xai-0.1.tar.gz
| Download URL | ml_shap_xai-0.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e241420e5507772824e7ff4b75259518e129ccff449a9999e34048b180f8df3f
|
|
BLAKE2b-256 checksum How to use checksums |
75a9910600dbd2d768d545b8882574e62c17fc41ad48d0805dfa879796c60906
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.12
|
Release files / ml_shap_xai-0.1-py3-none-any.whl
| Download URL | ml_shap_xai-0.1-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
657e364573ea83b0f41b3f6746ff7bb27a23b139be52993fef31cc52ea3c61a2
|
|
BLAKE2b-256 checksum How to use checksums |
ff8eb19ccedb6365a41acb0845bdf45173fcc3c93918fcb5b655abbf6203bd1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.12
|
Security for ml-shap-xai 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.
