Env Config Manager

• Outcome: Review
• Latest audit: May 28, 2026 · 3:38 AM UTC
• Version: 1.0.0

Overview

This skill is a plausible environment-file utility, but it handles secrets in ways users should review carefully before installing.

Install only if you are comfortable with the skill reading and modifying local .env files. Do not rely on the advertised encryption, key rotation, or team-safe sharing from these artifacts, and avoid running load, switch, get, or diff against real secret files unless output is redacted or you are in a private terminal/logging context.

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (11)

Missing User Warnings

Medium

• Confidence: 96% confidence
• Finding: The CLI prints every environment variable name and value when running the load and switch commands. Since .env files commonly contain API keys, database passwords, and tokens, this creates a direct secret-disclosure risk via terminal output, shell history capture, logs, CI job output, or other monitoring systems.

Missing User Warnings

Medium

• Confidence: 97% confidence
• Finding: The get and diff command paths echo individual variable values and before/after differences directly to stdout. This can leak secrets during local use, automation, or CI/CD execution, especially because diffs may expose rotated credentials and previous secret values that should no longer be visible.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

python-dotenv>=1.0.0
PyYAML>=6.0
cryptography>=41.0.0
click>=8.0.0

• Confidence: 95% confidence
• Finding: The dependency is specified with a lower-bound version only, so installs can resolve to different newer versions over time. This weakens build reproducibility and can unintentionally introduce vulnerable or incompatible releases through the supply chain.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

python-dotenv>=1.0.0
PyYAML>=6.0
cryptography>=41.0.0
click>=8.0.0
pytest>=7.0.0

• Confidence: 98% confidence
• Finding: PyYAML is not pinned to an exact version, which allows dependency resolution to drift. Because this package has a long history of security advisories, leaving it unpinned increases the chance of pulling a vulnerable release or having inconsistent environments.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

python-dotenv>=1.0.0
PyYAML>=6.0
cryptography>=41.0.0
click>=8.0.0
pytest>=7.0.0

• Confidence: 97% confidence
• Finding: cryptography is declared with only a minimum version, so future installs may fetch different versions and bundled components. For security-sensitive libraries, this creates supply-chain and reproducibility risk and can expose deployments to newly introduced vulnerable builds.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

python-dotenv>=1.0.0
PyYAML>=6.0
cryptography>=41.0.0
click>=8.0.0
pytest>=7.0.0

• Confidence: 90% confidence
• Finding: The click dependency is unpinned, which makes builds non-reproducible and increases supply-chain uncertainty. While this is usually lower severity than a directly vulnerable package, it still weakens dependency hygiene.

Unpinned Dependencies

Low

• Category: Supply Chain

Content

PyYAML>=6.0
cryptography>=41.0.0
click>=8.0.0
pytest>=7.0.0

• Confidence: 93% confidence
• Finding: pytest is unpinned, so different environments may install different versions with different security properties. Even though it is commonly a development dependency, vulnerable tooling can still affect CI systems and local development workflows.

Known Vulnerable Dependency: python-dotenv — 1 advisory(ies): CVE-2026-28684 (python-dotenv: Symlink following in set_key allows arbitrary file overwrite via )

Low

• Category: Supply Chain
• Confidence: 78% confidence
• Finding: The file permits installation of python-dotenv versions that may include an advisory affecting set_key symlink handling. If the skill or supporting tooling invokes that API on attacker-influenced paths, it could lead to arbitrary file overwrite in some environments.

Known Vulnerable Dependency: PyYAML — 8 advisory(ies): CVE-2019-20477 (Deserialization of Untrusted Data in PyYAML); CVE-2020-1747 (Improper Input Validation in PyYAML); CVE-2020-14343 (Improper Input Validation in PyYAML) +5 more

Critical

• Category: Supply Chain
• Confidence: 99% confidence
• Finding: PyYAML has multiple serious advisories, including unsafe deserialization risks that can lead to code execution when untrusted YAML is parsed insecurely. Because the requirement is broadly versioned and not pinned to a known-safe release, the skill may install an affected version, making this especially dangerous if any YAML input is processed.

Known Vulnerable Dependency: cryptography — 10 advisory(ies): GHSA-39hc-v87j-747x (Vulnerable OpenSSL included in cryptography wheels); CVE-2023-50782 (Python Cryptography package vulnerable to Bleichenbacher timing oracle attack); GHSA-5cpq-8wj7-hf2v (Vulnerable OpenSSL included in cryptography wheels) +7 more

High

• Category: Supply Chain
• Confidence: 96% confidence
• Finding: The cryptography package has multiple listed advisories, including issues in bundled OpenSSL components and cryptographic side-channel weaknesses. Since this library underpins sensitive security functions, installing an affected version can undermine confidentiality, integrity, or trust guarantees across the skill.

Known Vulnerable Dependency: pytest — 1 advisory(ies): CVE-2025-71176 (pytest has vulnerable tmpdir handling)

Low

• Category: Supply Chain
• Confidence: 82% confidence
• Finding: pytest is flagged for a tmpdir handling advisory, which can affect development or CI contexts if vulnerable versions are installed. This is less dangerous than a production runtime issue, but it can still expose build agents or test environments to filesystem-related abuse.

Static analysis

No suspicious patterns detected.