eunsujihoon-hub/safe-dotenv-check

Validate one or more .env files against a .env.example-style manifest.

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Jul 2, 2026
License: MIT

Pinned Snippet

workflow.ymlSHA-pinned

uses: eunsujihoon-hub/safe-dotenv-check@9104ff7f868553e11ba177f685564cba3e0e401a # v1.6.0

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
example	Path to the manifest file, usually .env.example.	yes	—
env_files	Newline-separated target .env file paths to validate.	yes	—
env_names	Optional newline-separated logical env names, once or once per env file.	no	""
allow_extra	Legacy alias for extra=ignore.	no	false
extra	How to handle keys that exist only in target env files. Use fail, warn, or ignore.	no	fail
show_descriptions	Set to true to include manifest desc/description text in reports.	no	false
redact_values	Set to true to omit invalid raw values from JSON reports.	no	true
summary	Set to true to write a markdown summary to the GitHub Actions step summary.	no	true
json_output_path	Optional path where the JSON report should be copied.	no	""

Outputs

name	description
ok	Whether all target files passed validation.
report_path	Path to the generated JSON report inside the runner workspace.