REGEXVAULTv2.0
Dev & Systems/Environment
Verified Safe

dotenv File Line Regex for Go

/^(?:export\s+)?([A-Za-z_][A-Za-z0-9_]{0,254})\s*=\s*(?:"([^"]*)"|'([^']*)'|([^#\n]*?))?\s*(?:#.*)?$/

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching dotenv file line, ported and verified for Go. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Go project — whether you're validating in a Gin handler, a gRPC service, or a command-line tool.

Go Implementation

Go
// dotenv File Line
// ReDoS-safe | RegexVault — Dev & Systems > Environment

package validation

import "regexp"

var dotenvFileLineRe = regexp.MustCompile(`^(?:export\s+)?([A-Za-z_][A-Za-z0-9_]{0,254})\s*=\s*(?:"([^"]*)"|'([^']*)'|([^#\n]*?))?\s*(?:#.*)?$`)

func ValidateDotenvFileLine(s string) bool {
    return dotenvFileLineRe.MatchString(s)
}

// Example
// fmt.Println(ValidateDotenvFileLine("NODE_ENV=production")) // true

Test Cases

Matches (Valid)
Rejects (Invalid)
NODE_ENV=production=value
PORT=3000 # comment1VAR=value
DB_URL="postgres://user:pass@db:5432/app"# this is a comment
export SECRET='my-secret'VAR NAME=value
EMPTY=

When to use this pattern

This pattern is drawn from the Dev & Systems > Environment category and carries a ReDoS-safe certification. That matters for Go developers because Go's RE2 engine is inherently safe from catastrophic backtracking, but this pattern has been additionally verified for correctness. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Multi-line values in double quotes are valid in some .env parsers but not others. Never commit .env files containing secrets to version control.

Technical Notes

Groups: 1=key, 2=double-quoted value, 3=single-quoted value, 4=unquoted value. Comment lines starting with # fail this pattern — skip them explicitly. Use a dedicated .env parser for production.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern