Confidential ML Utilities
Confidential ML is the practice of training machine learning models without seeing the training data. It is needed in many enterprises to satisfy the strict compliance and privacy guarantees they provide to their customers. This repository contains a set of utilities for confidential ML, with a special emphasis on using PyTorch in Azure Machine Learning pipelines.
⚠️Deprecation
This package has been deprecated as of May 2021. Please install pip install shrike and use shrike.compliant_logging instead. More details: https://github.com/Azure/shrike
Using
For more detailed examples and API reference, see the docs page.
Minimal use case:
from confidential_ml_utils import DataCategory, enable_confidential_logging, prefix_stack_trace
import logging
@prefix_stack_trace(allow_list=["FileNotFoundError", "SystemExit", "TypeError"])
def main():
enable_confidential_logging()
log = logging.getLogger(__name__)
log.info("Hi there", category=DataCategory.PUBLIC)
if __name__ == "__main__":
main()
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
2 maintainers
Metadata
2 maintainers
Release files for confidential-ml-utils 0.9.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 | |
|---|---|---|---|---|
| confidential-ml-utils-0.9.1.tar.gz | 9.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| confidential_ml_utils-0.9.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.8 kB
Release files / confidential-ml-utils-0.9.1.tar.gz
| Download URL | confidential-ml-utils-0.9.1.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0970049031ddbf1eda1523c87c9a5cdb5c477b4aeb9c3071e23518acd56035eb
|
|
BLAKE2b-256 checksum How to use checksums |
623066e35c79036a1304ee7b888e66649b4015ab9cf05e06227ad5d4674def8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.4.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.9.5
|
Release files / confidential_ml_utils-0.9.1-py3-none-any.whl
| Download URL | confidential_ml_utils-0.9.1-py3-none-any.whl |
|---|---|
| Size | 11.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8e2d9eccbb51ea1fb624e4cf641d13457f22fb90caf9f9bb2db50789c3a87788
|
|
BLAKE2b-256 checksum How to use checksums |
620eb0d70de2601445972405be129d495813706e4f617fe112d86b70d51dce63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.4.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.9.5
|
Security for confidential-ml-utils 0.9.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.
