dmno-dev/varlock

AI-safe .env files: Schemas for agents, Secrets for humans.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 4 minutes ago
Added to GitGenius on September 15th, 2026
Created on April 11th, 2025
Open Issues & Pull Requests: 58 (+0)
GitHub issues: Enabled
Number of forks: 121
Total Stargazers: 4,562 (+0)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.2 hours
Mean response time: 41.4 hours
90th percentile: 43.0 hours
Tracked items: 210

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 5% of issues opened in the past year have never received a reply. 78% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 82% of issues opened in the past year have been closed, leaving a working backlog. Three people close 90% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 36
New in 7 days: 6
Closed in 7 days: 1
Avg open age: 117 days
Stale 30+ days: 21
Stale 90+ days: 14

Recent activity

Opened in 7 days: 6
Closed in 7 days: 1
Comments in 7 days: 9
Events in 7 days: 18

Top labels

  • bug (75)
  • enhancement (75)
  • bun (1)
  • core:varlock (1)
  • plugin:1password (1)

Detailed Description

Varlock is a configuration management tool that applies schemas and validation to environment variable files while protecting secrets from exposure to AI agents and other tools.

The tool solves the problem of keeping environment configuration synchronized across teams and preventing accidental secret leaks, particularly in workflows involving AI code generation. It works by defining a single .env.schema file that serves as a source of truth for configuration structure, types, and validation rules. This schema can be shared and version-controlled without exposing actual secret values. The tool includes proactive leak scanning via command-line scanning and git hooks, runtime protection through log redaction and leak prevention, and a plugin system that enables secure declarative loading of secrets from external backends like 1Password, Infisical, AWS, Azure, GCP, and HCP Vault. Agents and AI tools can read the schema to understand configuration requirements without ever accessing the actual secrets.

Teams should adopt this tool if they need to manage environment variables across multiple environments, collaborate on configuration without syncing secrets, or integrate AI tools into their development workflow while maintaining security. It suits projects that require type safety and validation for environment variables, with IntelliSense support for developers. The tool replaces the traditional .env.example pattern with a living schema that stays synchronized with actual configuration needs.

The project maintains active continuous integration with automated testing. Development activity shows regular engagement with the community through a dedicated Discord chat channel. The tool is built on the @env-spec specification, which is documented separately and has an open RFC process for community input on the standard itself.