Env File Toolkit

• Outcome: Pass
• Latest audit: May 29, 2026 at 8:28 PM UTC
• Version:
  1.0.0

Overview

This is a local .env file utility whose sensitive behaviors are purpose-aligned and user-directed, but its outputs should be treated as secret-bearing.

Install only if you are comfortable with a local tool that can read .env files. Treat diff output, merge output, list-keys --with-values, and template --keep-values files as sensitive; avoid using them in shared logs, screenshots, tickets, or commits.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (7)

Lp3

Medium

• Category: MCP Least Privilege
• Confidence: 94% confidence
• Finding: The skill documents commands that read and write `.env` files, including generating templates and merged outputs, but the metadata declares no permissions. That mismatch can prevent proper policy review and user understanding of what the skill can access or modify, which is especially sensitive because `.env` files commonly contain secrets.

Missing User Warnings

Medium

• Confidence: 96% confidence
• Finding: The documented `template .env --keep-values` mode can copy real secret values into a generated template file, which users may mistakenly treat as safe to commit or share. In the context of `.env` management, preserving values without an explicit security warning materially increases the chance of credential disclosure.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: Documenting `list-keys .env --with-values` without warning encourages printing sensitive environment variable contents to terminal output, logs, screenshots, or command histories. Because `.env` files routinely store API keys, passwords, and tokens, exposing values in plaintext is risky even if intended for debugging.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The diff command prints raw .env values for added and changed keys directly to stdout. Because .env files commonly contain secrets such as API keys, tokens, and passwords, this can leak sensitive data into terminals, logs, shell history captures, CI job output, or other monitoring systems even during routine use.

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: The template command supports --keep-values, which writes the original .env values into a generated example file. Users may reasonably expect a template generator to scrub secrets, so this option can cause accidental persistence of production credentials into example files that are later committed, shared, or distributed.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The merge command emits merged key=value pairs either to stdout or to an output file with no masking or safety notice. Since merge is likely to be used on real environment files, this behavior can expose secrets in console logs or create plaintext secret files in unintended locations.

Missing User Warnings

Low

• Confidence: 89% confidence
• Finding: The list-keys command can print full values when --with-values is used, without indicating that secrets may be disclosed. This is less severe than automatic disclosure because the flag is explicit, but it still increases the chance of accidental credential exposure in logs and shared terminal output.

VirusTotal

52/52 vendors flagged this skill as clean.