| Name | envcloak JSON |
| Version |
0.3.0
JSON |
| download |
| home_page | None |
| Summary | Securely manage encrypted environment variables with ease. |
| upload_time | 2024-12-04 22:11:59 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.9 |
| license | Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2024 Konrad Kurek (Veinar) Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. |
| keywords |
environment-variables
encryption
security
cli-tool
python
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
<p align="center">
<img src="https://veinar.pl/envcloak.png" alt="logo" width="350"/>
</p>
<p align="center" style="background-color:#FF0000; color:white; padding:10px; border-radius:8px; font-size:14px; line-height:1.5;">
⚠️ <strong>IMPORTANT NOTE: EnvCloak is NOT Limited to .env Files!</strong>⚠️<br>
EnvCloak was originally built to secure <b>.env</b> files, but it can encrypt and decrypt <strong>any file type</strong>.<br>
Use it for <i>.json</i>, <i>.yaml</i>, <i>.txt</i>, <i>binary files</i>, or <i>any sensitive data.</i><br>
<br>
<span style="font-style:italic;">The name may be misleading, but the tool is far more versatile than it suggests!</span>
</p>
# 🔒 EnvCloak
> "Because Your Secrets Deserve Better Than Plaintext!"
[](https://codecov.io/gh/Veinar/envcloak)
[](https://www.codefactor.io/repository/github/veinar/envcloak)
[](https://www.bestpractices.dev/projects/9736)
Welcome to EnvCloak, the ultimate sidekick for developers, ops folks, and anyone who’s ever accidentally committed an API key to version control. (Yes, I know… it happens to the best of us. 😅) EnvCloak takes the stress out of managing environment variables by wrapping them in the cozy blanket of encryption, so you can focus on building awesome things—without the lingering fear of a security breach.
> If you find EnvCloak useful, please ⭐ the repository. It helps others discover this project! - thank you!
## 🛠️ Installation
In order to install `envcloak` simply run:
```bash
pip install envcloak
```
or if you want `dev` tools too 😎:
```bash
pip install envcloak[dev]
```
> 👋 There are also [self-contained binaries](examples/cli/README.md#get-yourself-a-envcloak-without-requirement-to-use-python-) for `Windows`, `Linux` and `MacOS`, don't have to use python at all! 🥳
## 🚀 Example Workflow
> ℹ️ More examples are present in [examples](./examples) section.
### Generating key:
```bash
# With password and salt
envcloak generate-key-from-password --password "YourTopSecretPassword" \
--salt "e3a1c8b0d4f6e2c7a5b9d6f0cr2ad1a2" --output secretkey.key
# With password without salt (we will add random salt then)
envcloak generate-key-from-password --password "YourTopSecretPassword" --output secretkey.key
# From random password and salt
envcloak generate-key --output secretkey.key
```
> **What it does:** generates your private key used to encrypt and decrypt files. **Appends (or creates if needed) .gitignore as well** as super-hero should! 🎉
> ⚠ **If someone knows your password and salt (option 1) can recreate same `key` - keep those variables safe as `key` itself** ⚠
### Encrypting Variables:
```bash
envcloak encrypt --input .env --output .env.enc --key-file mykey.key
```
> **What it does:** Encrypts your `.env` file with a specified key, outputting a sparkling `.env.enc` file.
### Decrypting Variables:
```bash
envcloak decrypt --input .env.enc --output .env --key-file mykey.key
```
> **What it does:** Decrypts the `.env.enc` file back to `.env` using the same key. Voilà!
or you may want to use it ...
### 🐍 In Your Python Code
```python
from envcloak import load_encrypted_env
load_encrypted_env('.env.enc', key_file='mykey.key').to_os_env()
# Now os.environ contains the decrypted variables
```
> **What it does:** Loads decrypted variables directly into `os.environ`. Secrets delivered, stress-free.
## 🛠️ Implementation Details
🔑 Encryption Algorithm
* Powered by AES-256-GCM for speed and security.
* Provides [`sha3` validation](docs/sha_validation.md) of files and content.
🗝️ Key Storage
* Local key files with strict permissions.
* Secure environment variables for CI/CD systems.
🗂️ File Handling
* Works with individual files.
* Works with directories using `--directory` instead of `--input` on `encrypt` and `decrypt`.
> ℹ️ EnvCloak process files in batch one-by-one.
* Can [recursively](docs/recursive.md) encrypt or decrypt directories.
* Can list files in directory that will be encrypted using `--preview` flag (ℹ️ only for directories and it does not commit the operation!).
🚦 Error Handling
* Clear, friendly error messages for any hiccups.
* Gracefully handles missing keys or corrupted files.
✅ Compatibility of pipelines and systems
* k8s / OKD / OCP deployments
* Jenkins pipelines
* Azure Pipelines
* Github Workflows
* Gitlab CI/CD Pipelines
## 🎉 Why EnvCloak?
Because you deserve peace of mind. EnvCloak wraps your environment variables in layers of encryption goodness, protecting them from prying eyes and accidental slips. Whether you’re a solo dev or part of a big team, this tool is here to make managing secrets simple, secure, and downright pleasant.
So go ahead—secure your `.env` like a boss. And remember, EnvCloak isn’t just a tool; it’s your secret-keeping partner in crime. (But the good kind of crime. 😎)
### Comparison of EnvCloak with Alternatives
| Tool | Strengths | Weaknesses |
|---------------|----------------------------------------|-----------------------------------------|
| **EnvCloak** | Lightweight, Python-native, simple to integrate with CI/CD workflows. | Limited ecosystem compared to established tools. |
| [**Sops**](https://github.com/mozilla/sops) | Integrates with cloud providers, supports partial file encryption. | More complex to configure for beginners. |
| [**BlackBox**](https://github.com/StackExchange/blackbox) | Simple file-based encryption for Git repos. | Limited to GPG, lacks flexibility. |
| [**Vault**](https://www.vaultproject.io/) | Robust, enterprise-grade with dynamic secrets. | High complexity, overkill for small projects. |
| [**Confidant**](https://lyft.github.io/confidant/) | AWS IAM integration, designed for secure CI/CD workflows. | Requires AWS, limited to its ecosystem. |
| [**Doppler**](https://www.doppler.com/) | Centralized secret management with CI/CD integration. | Paid plans for advanced features, cloud-reliant. |
> **Key Differentiator for EnvCloak**: Focused specifically on Python developers and lightweight CI/CD needs, making it ideal for small to medium projects.
## 🌟 Hall of Fame
A huge thanks to all our amazing contributors! 🎉
<a href="https://github.com/Veinar/envcloak/graphs/contributors">
<img src="https://contrib.rocks/image?repo=Veinar/envcloak"/>
</a>
## 🔗 Get Started Today!
Don’t let your API keys end up in the wrong hands (or on Twitter). Grab EnvCloak now and start encrypting like a pro.
Happy `env` Cloaking! 🕵️♂️
Raw data
{
"_id": null,
"home_page": null,
"name": "envcloak",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": null,
"keywords": "environment-variables, encryption, security, cli-tool, python",
"author": null,
"author_email": "\"Konrad Kurek (Veinar)\" <conrad.kurek+envcloak@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/db/75/a4c5e1edfe44e11791c9268ceb9c518cedcb813c27c2101b75713564774d/envcloak-0.3.0.tar.gz",
"platform": null,
"description": "\n<p align=\"center\">\n<img src=\"https://veinar.pl/envcloak.png\" alt=\"logo\" width=\"350\"/>\n</p>\n\n<p align=\"center\" style=\"background-color:#FF0000; color:white; padding:10px; border-radius:8px; font-size:14px; line-height:1.5;\">\n\u26a0\ufe0f <strong>IMPORTANT NOTE: EnvCloak is NOT Limited to .env Files!</strong>\u26a0\ufe0f<br> \nEnvCloak was originally built to secure <b>.env</b> files, but it can encrypt and decrypt <strong>any file type</strong>.<br>\nUse it for <i>.json</i>, <i>.yaml</i>, <i>.txt</i>, <i>binary files</i>, or <i>any sensitive data.</i><br>\n<br>\n<span style=\"font-style:italic;\">The name may be misleading, but the tool is far more versatile than it suggests!</span>\n</p>\n\n# \ud83d\udd12 EnvCloak\n\n> \"Because Your Secrets Deserve Better Than Plaintext!\"\n\n\n\n\n\n\n\n[](https://codecov.io/gh/Veinar/envcloak)\n[](https://www.codefactor.io/repository/github/veinar/envcloak)\n[](https://www.bestpractices.dev/projects/9736)\n\n\n\n\n\n\n\n\nWelcome to EnvCloak, the ultimate sidekick for developers, ops folks, and anyone who\u2019s ever accidentally committed an API key to version control. (Yes, I know\u2026 it happens to the best of us. \ud83d\ude05) EnvCloak takes the stress out of managing environment variables by wrapping them in the cozy blanket of encryption, so you can focus on building awesome things\u2014without the lingering fear of a security breach.\n\n> If you find EnvCloak useful, please \u2b50 the repository. It helps others discover this project! - thank you!\n\n## \ud83d\udee0\ufe0f Installation\n\nIn order to install `envcloak` simply run:\n```bash\npip install envcloak\n```\nor if you want `dev` tools too \ud83d\ude0e:\n```bash\npip install envcloak[dev]\n```\n\n> \ud83d\udc4b There are also [self-contained binaries](examples/cli/README.md#get-yourself-a-envcloak-without-requirement-to-use-python-) for `Windows`, `Linux` and `MacOS`, don't have to use python at all! \ud83e\udd73\n\n## \ud83d\ude80 Example Workflow\n\n> \u2139\ufe0f More examples are present in [examples](./examples) section.\n\n### Generating key:\n\n```bash\n# With password and salt\nenvcloak generate-key-from-password --password \"YourTopSecretPassword\" \\\n--salt \"e3a1c8b0d4f6e2c7a5b9d6f0cr2ad1a2\" --output secretkey.key\n\n# With password without salt (we will add random salt then)\nenvcloak generate-key-from-password --password \"YourTopSecretPassword\" --output secretkey.key\n\n# From random password and salt\nenvcloak generate-key --output secretkey.key\n```\n\n\n\n> **What it does:** generates your private key used to encrypt and decrypt files. **Appends (or creates if needed) .gitignore as well** as super-hero should! \ud83c\udf89\n\n> \u26a0 **If someone knows your password and salt (option 1) can recreate same `key` - keep those variables safe as `key` itself** \u26a0\n\n### Encrypting Variables:\n\n```bash\nenvcloak encrypt --input .env --output .env.enc --key-file mykey.key\n```\n\n\n\n> **What it does:** Encrypts your `.env` file with a specified key, outputting a sparkling `.env.enc` file.\n\n### Decrypting Variables:\n\n```bash\nenvcloak decrypt --input .env.enc --output .env --key-file mykey.key\n```\n\n\n\n> **What it does:** Decrypts the `.env.enc` file back to `.env` using the same key. Voil\u00e0!\n\nor you may want to use it ...\n\n### \ud83d\udc0d In Your Python Code\n\n```python\nfrom envcloak import load_encrypted_env\n\nload_encrypted_env('.env.enc', key_file='mykey.key').to_os_env()\n# Now os.environ contains the decrypted variables\n\n```\n> **What it does:** Loads decrypted variables directly into `os.environ`. Secrets delivered, stress-free.\n\n## \ud83d\udee0\ufe0f Implementation Details\n\ud83d\udd11 Encryption Algorithm\n\n* Powered by AES-256-GCM for speed and security.\n* Provides [`sha3` validation](docs/sha_validation.md) of files and content.\n\n\ud83d\udddd\ufe0f Key Storage\n\n* Local key files with strict permissions.\n* Secure environment variables for CI/CD systems.\n\n\ud83d\uddc2\ufe0f File Handling\n\n* Works with individual files.\n* Works with directories using `--directory` instead of `--input` on `encrypt` and `decrypt`.\n> \u2139\ufe0f EnvCloak process files in batch one-by-one. \n* Can [recursively](docs/recursive.md) encrypt or decrypt directories.\n* Can list files in directory that will be encrypted using `--preview` flag (\u2139\ufe0f only for directories and it does not commit the operation!).\n\n\ud83d\udea6 Error Handling\n\n* Clear, friendly error messages for any hiccups.\n* Gracefully handles missing keys or corrupted files.\n\n\u2705 Compatibility of pipelines and systems\n\n* k8s / OKD / OCP deployments\n* Jenkins pipelines\n* Azure Pipelines\n* Github Workflows\n* Gitlab CI/CD Pipelines\n\n\n## \ud83c\udf89 Why EnvCloak?\n\nBecause you deserve peace of mind. EnvCloak wraps your environment variables in layers of encryption goodness, protecting them from prying eyes and accidental slips. Whether you\u2019re a solo dev or part of a big team, this tool is here to make managing secrets simple, secure, and downright pleasant.\n\nSo go ahead\u2014secure your `.env` like a boss. And remember, EnvCloak isn\u2019t just a tool; it\u2019s your secret-keeping partner in crime. (But the good kind of crime. \ud83d\ude0e)\n\n### Comparison of EnvCloak with Alternatives\n\n| Tool | Strengths | Weaknesses |\n|---------------|----------------------------------------|-----------------------------------------|\n| **EnvCloak** | Lightweight, Python-native, simple to integrate with CI/CD workflows. | Limited ecosystem compared to established tools. |\n| [**Sops**](https://github.com/mozilla/sops) | Integrates with cloud providers, supports partial file encryption. | More complex to configure for beginners. |\n| [**BlackBox**](https://github.com/StackExchange/blackbox) | Simple file-based encryption for Git repos. | Limited to GPG, lacks flexibility. |\n| [**Vault**](https://www.vaultproject.io/) | Robust, enterprise-grade with dynamic secrets. | High complexity, overkill for small projects. |\n| [**Confidant**](https://lyft.github.io/confidant/) | AWS IAM integration, designed for secure CI/CD workflows. | Requires AWS, limited to its ecosystem. |\n| [**Doppler**](https://www.doppler.com/) | Centralized secret management with CI/CD integration. | Paid plans for advanced features, cloud-reliant. |\n\n> **Key Differentiator for EnvCloak**: Focused specifically on Python developers and lightweight CI/CD needs, making it ideal for small to medium projects.\n\n## \ud83c\udf1f Hall of Fame\n\nA huge thanks to all our amazing contributors! \ud83c\udf89\n\n<a href=\"https://github.com/Veinar/envcloak/graphs/contributors\">\n<img src=\"https://contrib.rocks/image?repo=Veinar/envcloak\"/>\n</a>\n\n## \ud83d\udd17 Get Started Today!\n\nDon\u2019t let your API keys end up in the wrong hands (or on Twitter). Grab EnvCloak now and start encrypting like a pro.\n\nHappy `env` Cloaking! \ud83d\udd75\ufe0f\u200d\u2642\ufe0f\n",
"bugtrack_url": null,
"license": "Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. \"License\" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. \"Licensor\" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. \"Legal Entity\" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, \"control\" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. \"You\" (or \"Your\") shall mean an individual or Legal Entity exercising permissions granted by this License. \"Source\" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. \"Object\" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. \"Work\" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). \"Derivative Works\" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. \"Contribution\" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, \"submitted\" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as \"Not a Contribution.\" \"Contributor\" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a \"NOTICE\" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets \"[]\" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same \"printed page\" as the copyright notice for easier identification within third-party archives. Copyright 2024 Konrad Kurek (Veinar) Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ",
"summary": "Securely manage encrypted environment variables with ease.",
"version": "0.3.0",
"project_urls": {
"Bug Tracker": "https://github.com/Veinar/envcloak/issues",
"Documentation": "https://github.com/Veinar/envcloak#readme",
"Homepage": "https://github.com/Veinar/envcloak"
},
"split_keywords": [
"environment-variables",
" encryption",
" security",
" cli-tool",
" python"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "7ee4bb86210062e7ef7a4e10f18cd884184b7a396419162091cf1f2e0481ed31",
"md5": "e4ce72f96f48d86f733f023cfdbc1d7d",
"sha256": "2554a36df12a89d388e9b3fb468b2691b6e06e4595fa4c89ca9b6dfff8122a12"
},
"downloads": -1,
"filename": "envcloak-0.3.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "e4ce72f96f48d86f733f023cfdbc1d7d",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 59075,
"upload_time": "2024-12-04T22:11:57",
"upload_time_iso_8601": "2024-12-04T22:11:57.388299Z",
"url": "https://files.pythonhosted.org/packages/7e/e4/bb86210062e7ef7a4e10f18cd884184b7a396419162091cf1f2e0481ed31/envcloak-0.3.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "db75a4c5e1edfe44e11791c9268ceb9c518cedcb813c27c2101b75713564774d",
"md5": "37d8b6c4dd3fa3a49e3255417993df15",
"sha256": "e24907c504406868ebfc53a0371dd079a18e248f1561cea608c829f785282386"
},
"downloads": -1,
"filename": "envcloak-0.3.0.tar.gz",
"has_sig": false,
"md5_digest": "37d8b6c4dd3fa3a49e3255417993df15",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 47262,
"upload_time": "2024-12-04T22:11:59",
"upload_time_iso_8601": "2024-12-04T22:11:59.175730Z",
"url": "https://files.pythonhosted.org/packages/db/75/a4c5e1edfe44e11791c9268ceb9c518cedcb813c27c2101b75713564774d/envcloak-0.3.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-12-04 22:11:59",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "Veinar",
"github_project": "envcloak",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "envcloak"
}
