env-guard — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited env-guard (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
env-guardian helps developers secure their environment configurations. It scans codebases for exposed secrets, generates .env templates from existing configs, validates environment variable setups against schemas, and rotates compromised secrets.
Activate this skill when the user asks to:
.env.example or .env.template file from an existing .env or codebaseScans the current project directory for exposed secrets, API keys, tokens, passwords, and other sensitive values hardcoded in source files. Returns a report of findings with file locations and severity levels.
Use when: The user wants to check for leaked secrets, audit security posture, or run a pre-commit secrets check.
Generates a .env.example or .env.template file by analyzing the current .env file or scanning source code for referenced environment variables. Strips actual values and adds descriptive comments.
Use when: The user wants to create a safe-to-commit env template, onboard new developers, or document required environment variables.
Validates the current environment configuration against a schema or expected set of variables. Checks for missing required variables, invalid formats, and type mismatches.
Use when: The user wants to verify their environment setup is correct, debug missing config issues, or enforce env var standards in CI.
Rotates compromised or expired secrets by generating new values and updating all references across the project. Supports common secret formats and integrates with secret managers.
Use when: The user needs to rotate API keys, database passwords, or other secrets after a security incident or as part of routine key rotation.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.