ML-Cloud-Tools - Code Doc
☁️ Machine Learning Tools for the Cloud. Currently very much focused on AWS and S3. ☁️
Table of Contents
- Installation
- Support and Feedback
- Reporting Security Vulnerabilities
- Contribution
- Code of Conduct
- Licensing
Installation
ML-Cloud-Tools is available at the Python Package Index (PyPI). It can be installed with pip:
$ pip install ml-cloud-tools
Support and Feedback
The following channels are available for discussions, feedback, and support requests:
Reporting Security Vulnerabilities
This project is built with security and data privacy in mind to ensure your data is safe. We are grateful for security researchers and users reporting a vulnerability to us, first. To ensure that your request is handled in a timely manner and non-disclosure of vulnerabilities can be assured, please follow the below guideline.
Please do not report security vulnerabilities directly on GitHub. GitHub Issues can be publicly seen and therefore would result in a direct disclosure.
Please address questions about data privacy, security concepts, and other media requests to the opensource@telekom.de mailbox.
Contribution
Our commitment to open source means that we are enabling - in fact encouraging - all interested parties to contribute and become part of our developer community.
Contribution and feedback is encouraged and always welcome. For more information about how to contribute, as well as additional contribution information, see our Contribution Guidelines.
Code of Conduct
This project has adopted the Contributor Covenant as our code of conduct. Please see the details in our Contributor Covenant Code of Conduct. All contributors must abide by the code of conduct.
Licensing
Copyright (c) 2021 Timothy Wolff-Piggott, Deutsche Telekom AG
Copyright (c) 2021-2023 Philip May, Deutsche Telekom AG
Copyright (c) 2021-2023 Philip May
Licensed under the MIT License (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License by reviewing the file LICENSE in the repository.
Release files for ml-cloud-tools 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 | |
|---|---|---|---|---|
| ml_cloud_tools-0.0.1.tar.gz | 12.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ml_cloud_tools-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.6 kB
Release files / ml_cloud_tools-0.0.1.tar.gz
| Download URL | ml_cloud_tools-0.0.1.tar.gz |
|---|---|
| Size | 12.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f72ea47de050843a3dc531f368fd7625bdc16cb76a27a506102101f4cb0fbfe
|
|
BLAKE2b-256 checksum How to use checksums |
922f34a048c8188e355ee38a2f6f966a0d5dc8becbad120ecbb58ea1b2258c5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / ml_cloud_tools-0.0.1-py3-none-any.whl
| Download URL | ml_cloud_tools-0.0.1-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0226667b17c29082de418fb744503760c31030f1af14baa7ea6543cee2214d10
|
|
BLAKE2b-256 checksum How to use checksums |
e6dac311e6606301a9aca9bae7d27520ba37ecdd26e67602d3de909aaadb670e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for ml-cloud-tools 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.
