Cómo usar: .env.example Generator
- Paste your
.env(it never leaves the browser), or switch to From source code and paste code. - Secrets such as keys, tokens, passwords and connection strings are blanked; safe values like
PORT=3000are kept. - Review the summary of what was removed, kept and flagged.
- Copy or download the
.env.exampleand commit it.
Why commit a .env.example?
A .env file holds secrets and must never be committed. But new team members, CI and deployment platforms still need to know which variables exist. A .env.example (also called .env.sample or .env.template) lists every key with placeholder values and comments, so anyone can copy it to .env and fill in their own values.
How secrets are detected
- Key names containing SECRET, TOKEN, PASSWORD, PASS, PWD, KEY, PRIVATE, CREDENTIAL, AUTH, SALT, DSN or WEBHOOK.
- Value patterns such as Stripe (
sk_live_…), GitHub (ghp_…), AWS (AKIA…), Slack, OpenAI and Anthropic keys, JWTs, PEM private keys and URLs with embedded passwords (postgres://user:pass@…). - High-entropy strings — long random-looking values are treated as secrets even if the key name looks harmless.
Safe defaults (ports, log levels, NODE_ENV, booleans, localhost URLs) are kept so the example works out of the box. Check the finished file with the .env file validator, and keep .env out of Git with the .gitignore generator.
También se busca como: .env.example, generate env example, env template, dotenv example, remove secrets from env, find environment variables in code.
Herramientas que combinan con: .env.example Generator
- Dockerfile Generator — Choose your stack and get a production-ready Dockerfile: multi-stage build, cached dependency layer, non-root user, health check and a matching .dockerignore — explained line by line.
- Generador de Docker Compose — Marca los servicios que necesites —aplicación, base de datos, caché, interfaz de administración, receptor de correo— y obtén un archivo `compose.yaml` limpio con imágenes fijadas, volúmenes con nombre, comprobaciones de estado y depends_on condiciones, además de un archivo .env a juego con contraseñas generadas.
- GitHub Actions Workflow Validator — Paste a workflow from .github/workflows and find problems before CI does — invalid triggers, missing runs-on, broken needs, bad expressions, outdated actions and script-injection risks.
- YAML Validator — Paste a Docker Compose file, Kubernetes manifest, GitHub Actions workflow or any YAML to pinpoint errors, catch common pitfalls and get a cleanly formatted version.
Preguntas frecuentes
Is my .env file uploaded?
No. Everything runs in your browser. Still, if a real production secret was ever committed or shared, rotate it.
Which languages does code scanning support?
JavaScript and TypeScript (
process.env.X, process.env["X"], import.meta.env.X, Deno.env.get), Python (os.environ, os.getenv), Go (os.Getenv), Ruby (ENV["X"]), PHP (getenv, $_ENV), Rust (env::var), Java (System.getenv), C# and Docker Compose ${VAR} references.What are the type hints?
Short comments such as
# number, # boolean or # url derived from the original value, so whoever fills in the file knows what format is expected.¿Puedo instalar .env.example Generator como aplicación web y utilizarla sin conexión?
Sí. .env.example Generator es una aplicación web instalable (PWA): se instala desde el navegador, no se descarga desde una tienda de aplicaciones. Haz clic en «Instalar aplicación» en la parte superior de esta página en Chrome o Edge (Windows, macOS, Linux, ChromeOS) o, en Android, utiliza «Compartir» → «Añadir a la pantalla de inicio» en iPhone y iPad, o «Archivo» → «Añadir al Dock» en Safari 17+ en un Mac. A continuación, se abrirá en su propia ventana con su propio icono y, como se ejecuta íntegramente en tu navegador, seguirá funcionando sin conexión. Firefox en el ordenador de sobremesa no permite instalar aplicaciones web. Cómo funciona la instalación.