| Name | envshield JSON |
| Version |
2.0.0
JSON |
| download |
| home_page | None |
| Summary | EnvShield: A CLI for secure local environment management and secret prevention. |
| upload_time | 2025-09-13 13:27:54 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.10 |
| license | MIT License
Copyright (c) [2025] [Rabbil Yasar Sajal]
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE. |
| keywords |
environment
security
secrets
cli
devops
|
| VCS |
|
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# EnvShield 🛡️
[](https://github.com/rabbilyasar/envshield/actions/workflows/ci.yml)
[](https://pypi.org/project/envshield/)
[](https://opensource.org/licenses/MIT)
[](https://pepy.tech/project/envshield)
[](https://www.envshield.dev)
**Stop setting your project on fire 🔥. Let's talk about your environment.**
Ever had that 3 AM, caffeine-fueled moment of panic 😱, wondering if you just pushed the entire company's AWS account to a public repo? I've definitely been there.
EnvShield is the command-line co-pilot that saves you from yourself. It automates the chaotic ritual of managing environment variables, documents your configuration for you, and acts as the slightly over-attached guardian angel for your secrets.
### Table of Contents
1. [Why Bother? (The Problem We All Ignore)](#why-bother-the-problem-we-all-ignore)
2. [The EnvShield Philosophy: Schema-First Configuration](#the-envshield-philosophy-schema-first-configuration)
3. [How EnvShield is Different (Competitor Smackdown)](#how-envshield-is-different-competitor-smackdown)
4. [Installation](#installation)
5. [The Spellbook: A Guide to the Commands](#the-spellbook-a-guide-to-the-commands)
6. [The Brains of the Operation: The Core Files](#the-brains-of-the-operation-the-core-files)
7. [The Future: Teams & Enterprise](#the-future-teams--enterprise)
8. [Community & Contributing](#community--contributing)
## Why Bother? (The Problem We All Ignore)
Let's be honest, managing environment configuration is often a dumpster fire 🔥. It's a mess of manually copied `.env` files, outdated `.env.example` templates, and that one Slack DM with the production key that you really hope nobody finds.
This isn't just annoying; it's how disasters happen. A single leaked key can cost millions. EnvShield exists to make the secure and documented way the easiest and laziest way.
## The EnvShield Philosophy: Schema-First Configuration
EnvShield's power comes from a simple idea: your configuration should be treated like code. It introduces a single source of truth, the `env.schema.toml` file.
This file is a **contract** that explicitly defines every environment variable your project needs. By defining your variables here, you get:
- **Automated Documentation**: Your `.env.example` is always perfectly in sync.
- **Ironclad Validation**: Catch typos and missing variables before you run your app.
- **Proactive Security**: A built-in scanner and Git hook prevent secrets from ever being committed.
## How EnvShield is Different (Competitor Smackdown)
A scanner is a smoke detector. A cloud vault is an off-site bank. **EnvShield is the fireproof, self-organizing house you should have been living in all along.** It provides the complete local workflow that developers need.
| | | | | |
| ----------------------------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------- | --------------------------------- |
| **Developer Pain Point** | **EnvShield** 🛡️ | **TruffleHog / Gitleaks** | **Doppler / Infisical** | **direnv** |
| **Preventing Secret Commits** | ✅ **Built-in**. The **init** command sets up an automated pre-commit hook. | ✅ **Core feature**. Specialized tools for finding secrets. | ❌ **Indirectly**. Encourages not having secret files, but doesn't actively scan commits. | ❌ **Not addressed.** |
| **New Developer Setup** | ✅ Automated. The `setup` command interactively creates a local `.env` file from the example. | ❌ **Not addressed.** | ✅ **Strong**. Provides a central place to get secrets, but doesn't manage local files. | ❌ **Not addressed.** |
| **Handling Config Drift** | ✅ **Solved**. The schema is the source of truth. `schema sync` and `check` enforce consistency. | ❌ **Not addressed.** | ✅ **Solved**. The cloud is the single source of truth. | ❌ **Not addressed.** |
| **Primary Focus** | **Complete Local Workflow**. Manages files, documents schemas, validates setups, and scans for leaks. | **Secret Detection Engine.** | **Cloud-Based Secret** Vault. | **Shell Environment Automation.** |
## Installation
You'll need Python 3.10+.
```
pip install envshield
```
Check if the magic worked: `envshield --help`
## The Spellbook: A Guide to the Commands
These are the core commands for the free, local-only Phase 1.
### `envshield init`
The "zero-to-hero" command. Run this first in a new or existing project.
- **What it does:** Intelligently inspects your project to detect the framework (e.g., Next.js, Python/Django) and scaffolds a complete, best-practice configuration foundation. It creates your `env.schema.toml` with smart defaults, updates your `.gitignore`, and automatically installs the security hook.
- **Flags**:
- `--force` / `-f`: Overwrites existing EnvShield files. It will ask for confirmation before nuking your setup.
- **Real-Life Example**: You're starting a new Django project. You run `envshield init`. The tool detects Django, creates a schema with `SECRET_KEY` and `DATABASE_URL`, and installs the security hook. Your project is set up for success in one command.
### `envshield scan`
Your project's personal bodyguard. It scans files for hardcoded secrets.
- **What it does**: Uses a comprehensive list of patterns to find things that look like API keys, private keys, and other credentials.
- **Arguments & Flags**:
- `[PATHS]...`: The specific files or directories to scan. Defaults to the current directory.
- **Use Case**: You've been working on a new module and want to be extra careful: `envshield scan src/billing/`
- `--staged`: Scans only the files you've staged for your next Git commit. This is the heart of the pre-commit hook.
- **Use Case**: This is run automatically by the hook every time you `git commit`. If you accidentally staged a file with a secret, the commit is blocked, saving you from a very bad day.
- `--config <file>`: Use a different `envshield.yml` for this specific scan.
- **Use Case:** Your CI/CD pipeline needs to run a scan but should ignore test files. You run `envshield scan . --config .github/ci.envshield.yml` to use a special configuration just for that run.
### `envshield install-hook`
Manually installs the Git pre-commit hook if you skipped it during `init` or if your project had an existing hook.
- **What it does**: Creates a `pre-commit` script in your `.git/hooks/` directory that runs `envshield scan --staged`.
- **Real-Life Example**: You've added `envshield` to a project that already uses a code formatting hook. You can manually merge the two scripts and then run `envshield install-hook --force` to create the combined hook.
### `envshield check <file>`
The "is it plugged in?" command for your local setup.
- **What it does**: Validates a local environment file (e.g., `.env`) against the official contract in `env.schema.toml`. It reports missing or extra variables, intelligently ignoring variables that have a `defaultValue` in the schema.
- **Real-Life Example**: Your app fails to start after a teammate's PR. You run `envshield check`. The tool reports `Missing in Local: NEW_SERVICE_API_KEY`, instantly telling you what's wrong.
### `envshield schema sync`
The project librarian. It ensures your public-facing documentation is never out of date.
- **What it does:** Reads your `env.schema.toml` and generates a perfect `.env.example` file, complete with comments from your variable descriptions.
- **Real-Life Example**: You add a new `REDIS_URL` variable to your schema. Instead of manually updating the example file, you just run `envshield schema sync`. The `.env.example` is instantly and correctly updated, ready to be committed.
### `envshield setup`
A taste of the automated onboarding magic.
- **What it does**: The perfect command for getting started. It reads your `.env.example` file, finds any variables without a value, and interactively prompts you for them. It then generates your first `.env` file.
- **Real-Life Example**: You just cloned a new project. You run `envshield setup`. The tool asks you for the `DATABASE_URL` and `STRIPE_API_KEY`, then generates your fully-populated `.env` file. You are ready to run the project in minutes.
### `envshield doctor`
The "turn it off and on again" command for your entire configuration.
- **What it does**: Runs a comprehensive suite of health checks on your project's `envshield` setup. It checks for missing config files, validates your local environment against the schema, ensures your `.env.example` is in sync, and verifies that the security hook is installed correctly.
- **Flags**:
- `--fix`: The magic wand. If the doctor finds a problem (like a missing hook or an out-of-date example file), it will interactively ask you if you want to fix it automatically.
- **Real-Life Example**: Something just feels wrong with your setup. You run `envshield doctor`. It reports that your `.env.example` is out of date and the Git hook is missing. You run `envshield doctor --fix`, answer "Yes" to both prompts, and the tool fixes everything for you.
## The Brains of the Operation: The Core Files
`envshield` is managed by two simple files you commit to your repository.
- `env.schema.toml`: The source of truth. This is where you define every variable your project needs.
```
# env.schema.toml
[DATABASE_URL]
description = "The full connection string for the PostgreSQL database."
secret = true # Marks this as sensitive
[LOG_LEVEL]
description = "Controls the application's log verbosity."
secret = false
defaultValue = "info" # Provides a fallback
```
- `envshield.yml`: The workflow config. In Phase 1, it's very simple and mainly points to your schema and defines scanner exclusions.
## The Future: Teams & Enterprise ✨
Phase 1 is the free, powerful "Local Guardian." But the journey doesn't end there. Upcoming paid tiers will turn `envshield` into a complete collaboration and automation platform.
### Phase 2: The Team Collaborator (Paid Tier)
- `envshield use <profile>`: Instantly switch your entire project's configuration between different environments (e.g., `local`, `staging`).
- `envshield onboard <profile>`: A supercharged `setup` that can also run scripts like` docker compose up` and database migrations for a true one-command setup.
- `envshield share`: Securely share a secret with a teammate via an encrypted, one-time-use link.
- `envshield docs`: Generate beautiful Markdown or HTML documentation from your schema.
### Phase 3: The Enterprise-Grade System (Paid Tier)
- `envshield login`, `pull`, `push`: Full integration with a centralized, cloud-based secret vault.
- `envshield export`: Securely inject secrets into your CI/CD pipelines for automated deployments.
- **Audit Logs & RBAC**: A complete, compliant, and auditable history of all secret access and team permissions, managed through a web dashboard.
## **Community & Support**
Got questions? Have a brilliant idea? Come hang out with us!
* 🤔 **Ask a question on GitHub Discussions:**[Discussions](https://github.com/rabbilyasar/envshield/discussions/)
Or, Follow us on our socials:
## 🌍 Community & Links
- 🌐 Website: [envshield.dev](https://www.envshield.dev)
- 🐙 GitHub: [rabbilyasar/envshield](https://github.com/rabbilyasar/envshield)
- 🐍 PyPI: [EnvShield on PyPI](https://pypi.org/project/envshield/)
- 🤔 GitHub Discussions: [GitHub Discussions](https://github.com/rabbilyasar/envshield/discussions)
- 💬 Join our Discord:[@discord](https://discord.gg/dSEbvPW57N)
## **Contributing (Don't Be Shy)**
Spotted a bug? Think our jokes are terrible? We want to hear it all. Check out `CONTRIBUTING.md` to get started.
Raw data
{
"_id": null,
"home_page": null,
"name": "envshield",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": null,
"keywords": "environment, security, secrets, cli, devops",
"author": null,
"author_email": "Rabbil Yasar Sajal <rabbilyasar@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/1c/58/1b1ce6737da33539427d2de3594a4ffee7219c4c0f7c8f03a4f2141fc0a9/envshield-2.0.0.tar.gz",
"platform": null,
"description": "\n# EnvShield \ud83d\udee1\ufe0f\n\n[](https://github.com/rabbilyasar/envshield/actions/workflows/ci.yml)\n[](https://pypi.org/project/envshield/)\n[](https://opensource.org/licenses/MIT)\n[](https://pepy.tech/project/envshield)\n[](https://www.envshield.dev)\n\n\n**Stop setting your project on fire \ud83d\udd25. Let's talk about your environment.**\n\n\n\nEver had that 3 AM, caffeine-fueled moment of panic \ud83d\ude31, wondering if you just pushed the entire company's AWS account to a public repo? I've definitely been there.\n\nEnvShield is the command-line co-pilot that saves you from yourself. It automates the chaotic ritual of managing environment variables, documents your configuration for you, and acts as the slightly over-attached guardian angel for your secrets.\n\n### Table of Contents\n\n1. [Why Bother? (The Problem We All Ignore)](#why-bother-the-problem-we-all-ignore)\n \n2. [The EnvShield Philosophy: Schema-First Configuration](#the-envshield-philosophy-schema-first-configuration)\n \n3. [How EnvShield is Different (Competitor Smackdown)](#how-envshield-is-different-competitor-smackdown)\n \n4. [Installation](#installation)\n \n5. [The Spellbook: A Guide to the Commands](#the-spellbook-a-guide-to-the-commands)\n \n6. [The Brains of the Operation: The Core Files](#the-brains-of-the-operation-the-core-files)\n \n7. [The Future: Teams & Enterprise](#the-future-teams--enterprise)\n \n8. [Community & Contributing](#community--contributing)\n \n\n## Why Bother? (The Problem We All Ignore)\n\nLet's be honest, managing environment configuration is often a dumpster fire \ud83d\udd25. It's a mess of manually copied `.env` files, outdated `.env.example` templates, and that one Slack DM with the production key that you really hope nobody finds.\n\nThis isn't just annoying; it's how disasters happen. A single leaked key can cost millions. EnvShield exists to make the secure and documented way the easiest and laziest way.\n\n## The EnvShield Philosophy: Schema-First Configuration\n\nEnvShield's power comes from a simple idea: your configuration should be treated like code. It introduces a single source of truth, the `env.schema.toml` file.\n\nThis file is a **contract** that explicitly defines every environment variable your project needs. By defining your variables here, you get:\n\n- **Automated Documentation**: Your `.env.example` is always perfectly in sync.\n \n- **Ironclad Validation**: Catch typos and missing variables before you run your app.\n \n- **Proactive Security**: A built-in scanner and Git hook prevent secrets from ever being committed.\n \n\n## How EnvShield is Different (Competitor Smackdown)\n\nA scanner is a smoke detector. A cloud vault is an off-site bank. **EnvShield is the fireproof, self-organizing house you should have been living in all along.** It provides the complete local workflow that developers need.\n\n| | | | | |\n| ----------------------------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------- | --------------------------------- |\n| **Developer Pain Point** | **EnvShield** \ud83d\udee1\ufe0f | **TruffleHog / Gitleaks** | **Doppler / Infisical** | **direnv** |\n| **Preventing Secret Commits** | \u2705 **Built-in**. The **init** command sets up an automated pre-commit hook. | \u2705 **Core feature**. Specialized tools for finding secrets. | \u274c **Indirectly**. Encourages not having secret files, but doesn't actively scan commits. | \u274c **Not addressed.** |\n| **New Developer Setup** | \u2705 Automated. The `setup` command interactively creates a local `.env` file from the example. | \u274c **Not addressed.** | \u2705 **Strong**. Provides a central place to get secrets, but doesn't manage local files. | \u274c **Not addressed.** |\n| **Handling Config Drift** | \u2705 **Solved**. The schema is the source of truth. `schema sync` and `check` enforce consistency. | \u274c **Not addressed.** | \u2705 **Solved**. The cloud is the single source of truth. | \u274c **Not addressed.** |\n| **Primary Focus** | **Complete Local Workflow**. Manages files, documents schemas, validates setups, and scans for leaks. | **Secret Detection Engine.** | **Cloud-Based Secret** Vault. | **Shell Environment Automation.** |\n\n## Installation\n\nYou'll need Python 3.10+.\n\n```\npip install envshield\n```\n \n\nCheck if the magic worked: `envshield --help`\n\n## The Spellbook: A Guide to the Commands\n\nThese are the core commands for the free, local-only Phase 1.\n\n### `envshield init`\n\nThe \"zero-to-hero\" command. Run this first in a new or existing project.\n\n- **What it does:** Intelligently inspects your project to detect the framework (e.g., Next.js, Python/Django) and scaffolds a complete, best-practice configuration foundation. It creates your `env.schema.toml` with smart defaults, updates your `.gitignore`, and automatically installs the security hook.\n\n- **Flags**:\n\n- `--force` / `-f`: Overwrites existing EnvShield files. It will ask for confirmation before nuking your setup.\n\n- **Real-Life Example**: You're starting a new Django project. You run `envshield init`. The tool detects Django, creates a schema with `SECRET_KEY` and `DATABASE_URL`, and installs the security hook. Your project is set up for success in one command.\n\n### `envshield scan`\n\nYour project's personal bodyguard. It scans files for hardcoded secrets.\n\n- **What it does**: Uses a comprehensive list of patterns to find things that look like API keys, private keys, and other credentials.\n\n- **Arguments & Flags**:\n\n- `[PATHS]...`: The specific files or directories to scan. Defaults to the current directory.\n\n\t- **Use Case**: You've been working on a new module and want to be extra careful: `envshield scan src/billing/`\n\n- `--staged`: Scans only the files you've staged for your next Git commit. This is the heart of the pre-commit hook.\n \n\t- **Use Case**: This is run automatically by the hook every time you `git commit`. If you accidentally staged a file with a secret, the commit is blocked, saving you from a very bad day.\n\n- `--config <file>`: Use a different `envshield.yml` for this specific scan.\n\n\t- **Use Case:** Your CI/CD pipeline needs to run a scan but should ignore test files. You run `envshield scan . --config .github/ci.envshield.yml` to use a special configuration just for that run.\n\n### `envshield install-hook`\n\nManually installs the Git pre-commit hook if you skipped it during `init` or if your project had an existing hook.\n\n- **What it does**: Creates a `pre-commit` script in your `.git/hooks/` directory that runs `envshield scan --staged`.\n \n- **Real-Life Example**: You've added `envshield` to a project that already uses a code formatting hook. You can manually merge the two scripts and then run `envshield install-hook --force` to create the combined hook.\n\n### `envshield check <file>`\n\nThe \"is it plugged in?\" command for your local setup.\n\n- **What it does**: Validates a local environment file (e.g., `.env`) against the official contract in `env.schema.toml`. It reports missing or extra variables, intelligently ignoring variables that have a `defaultValue` in the schema.\n \n- **Real-Life Example**: Your app fails to start after a teammate's PR. You run `envshield check`. The tool reports `Missing in Local: NEW_SERVICE_API_KEY`, instantly telling you what's wrong.\n \n\n### `envshield schema sync`\n\nThe project librarian. It ensures your public-facing documentation is never out of date.\n\n- **What it does:** Reads your `env.schema.toml` and generates a perfect `.env.example` file, complete with comments from your variable descriptions.\n \n- **Real-Life Example**: You add a new `REDIS_URL` variable to your schema. Instead of manually updating the example file, you just run `envshield schema sync`. The `.env.example` is instantly and correctly updated, ready to be committed.\n \n\n### `envshield setup`\n\nA taste of the automated onboarding magic.\n\n\n\n- **What it does**: The perfect command for getting started. It reads your `.env.example` file, finds any variables without a value, and interactively prompts you for them. It then generates your first `.env` file.\n \n- **Real-Life Example**: You just cloned a new project. You run `envshield setup`. The tool asks you for the `DATABASE_URL` and `STRIPE_API_KEY`, then generates your fully-populated `.env` file. You are ready to run the project in minutes.\n\n### `envshield doctor`\n\nThe \"turn it off and on again\" command for your entire configuration.\n\n\n\n- **What it does**: Runs a comprehensive suite of health checks on your project's `envshield` setup. It checks for missing config files, validates your local environment against the schema, ensures your `.env.example` is in sync, and verifies that the security hook is installed correctly.\n \n- **Flags**:\n \n - `--fix`: The magic wand. If the doctor finds a problem (like a missing hook or an out-of-date example file), it will interactively ask you if you want to fix it automatically.\n \n- **Real-Life Example**: Something just feels wrong with your setup. You run `envshield doctor`. It reports that your `.env.example` is out of date and the Git hook is missing. You run `envshield doctor --fix`, answer \"Yes\" to both prompts, and the tool fixes everything for you.\n\n## The Brains of the Operation: The Core Files\n\n`envshield` is managed by two simple files you commit to your repository.\n\n- `env.schema.toml`: The source of truth. This is where you define every variable your project needs.\n\n```\n # env.schema.toml \n \n [DATABASE_URL] \n description = \"The full connection string for the PostgreSQL database.\" \n secret = true # Marks this as sensitive \n \n [LOG_LEVEL] \n description = \"Controls the application's log verbosity.\" \n secret = false \n defaultValue = \"info\" # Provides a fallback \n```\n\n- `envshield.yml`: The workflow config. In Phase 1, it's very simple and mainly points to your schema and defines scanner exclusions.\n \n\n## The Future: Teams & Enterprise \u2728\n\nPhase 1 is the free, powerful \"Local Guardian.\" But the journey doesn't end there. Upcoming paid tiers will turn `envshield` into a complete collaboration and automation platform.\n\n### Phase 2: The Team Collaborator (Paid Tier)\n\n- `envshield use <profile>`: Instantly switch your entire project's configuration between different environments (e.g., `local`, `staging`).\n \n- `envshield onboard <profile>`: A supercharged `setup` that can also run scripts like` docker compose up` and database migrations for a true one-command setup.\n \n- `envshield share`: Securely share a secret with a teammate via an encrypted, one-time-use link.\n \n- `envshield docs`: Generate beautiful Markdown or HTML documentation from your schema.\n \n### Phase 3: The Enterprise-Grade System (Paid Tier)\n\n- `envshield login`, `pull`, `push`: Full integration with a centralized, cloud-based secret vault.\n \n- `envshield export`: Securely inject secrets into your CI/CD pipelines for automated deployments.\n \n- **Audit Logs & RBAC**: A complete, compliant, and auditable history of all secret access and team permissions, managed through a web dashboard.\n\n## **Community & Support**\n\nGot questions? Have a brilliant idea? Come hang out with us!\n\n* \ud83e\udd14 **Ask a question on GitHub Discussions:**[Discussions](https://github.com/rabbilyasar/envshield/discussions/)\n\nOr, Follow us on our socials:\n## \ud83c\udf0d Community & Links\n\n- \ud83c\udf10 Website: [envshield.dev](https://www.envshield.dev) \u00a0\n- \ud83d\udc19 GitHub: [rabbilyasar/envshield](https://github.com/rabbilyasar/envshield) \u00a0\n- \ud83d\udc0d PyPI: [EnvShield on PyPI](https://pypi.org/project/envshield/) \u00a0\n- \ud83e\udd14 GitHub Discussions: [GitHub Discussions](https://github.com/rabbilyasar/envshield/discussions) \u00a0\n- \ud83d\udcac Join our Discord:[@discord](https://discord.gg/dSEbvPW57N) \u00a0\n## **Contributing (Don't Be Shy)**\n\nSpotted a bug? Think our jokes are terrible? We want to hear it all. Check out `CONTRIBUTING.md` to get started.\n",
"bugtrack_url": null,
"license": "MIT License\n \n Copyright (c) [2025] [Rabbil Yasar Sajal] \n \n Permission is hereby granted, free of charge, to any person obtaining a copy\n of this software and associated documentation files (the \"Software\"), to deal\n in the Software without restriction, including without limitation the rights\n to use, copy, modify, merge, publish, distribute, sublicense, and/or sell\n copies of the Software, and to permit persons to whom the Software is\n furnished to do so, subject to the following conditions:\n \n The above copyright notice and this permission notice shall be included in all\n copies or substantial portions of the Software.\n \n THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\n IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\n FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\n AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\n LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\n OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\n SOFTWARE.",
"summary": "EnvShield: A CLI for secure local environment management and secret prevention.",
"version": "2.0.0",
"project_urls": null,
"split_keywords": [
"environment",
" security",
" secrets",
" cli",
" devops"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "f85004ea2d87de99e99e9fde204c2ca271af5ae15b1a127151e37fb1248e9e68",
"md5": "a8bdaf9d968ad92b0b4dfc09575605e8",
"sha256": "fd32437b039f5dd092ea6a9b9b42ee98907aa4030eeface01cf45265ff548ccf"
},
"downloads": -1,
"filename": "envshield-2.0.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "a8bdaf9d968ad92b0b4dfc09575605e8",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 36732,
"upload_time": "2025-09-13T13:27:52",
"upload_time_iso_8601": "2025-09-13T13:27:52.839977Z",
"url": "https://files.pythonhosted.org/packages/f8/50/04ea2d87de99e99e9fde204c2ca271af5ae15b1a127151e37fb1248e9e68/envshield-2.0.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "1c581b1ce6737da33539427d2de3594a4ffee7219c4c0f7c8f03a4f2141fc0a9",
"md5": "3f6acea165c250c8edb9d01d27842768",
"sha256": "a8dbe58ae36c88dc18e2a2eecfbdaefc3dac205d9aade890a331279faafe66fa"
},
"downloads": -1,
"filename": "envshield-2.0.0.tar.gz",
"has_sig": false,
"md5_digest": "3f6acea165c250c8edb9d01d27842768",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.10",
"size": 33050,
"upload_time": "2025-09-13T13:27:54",
"upload_time_iso_8601": "2025-09-13T13:27:54.748046Z",
"url": "https://files.pythonhosted.org/packages/1c/58/1b1ce6737da33539427d2de3594a4ffee7219c4c0f7c8f03a4f2141fc0a9/envshield-2.0.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-09-13 13:27:54",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "envshield"
}
