varlock.dev valid
Varlock
Varlock is an open source CLI and library for AI-safe .env files. A .env.schema declares and validates environment variables, secrets are encrypted locally or loaded from external providers, and redaction plus a credential proxy keep secret values away from logs, terminals, and AI agents.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T06:00:37.773Z. Cached copy · Source on varlock.dev
# Varlock
> Varlock is an open source CLI and library for AI-safe .env files. A .env.schema declares and validates environment variables, secrets are encrypted locally or loaded from external providers, and redaction plus a credential proxy keep secret values away from logs, terminals, and AI agents.
When to use varlock:
- Managing .env files across development, CI, and production environments
- Declaring env vars in a .env.schema with decorators like @type, @required, and @sensitive
- Validating configuration at startup so misconfiguration fails early with clear errors
- Encrypting local overrides in .env.local so nothing sensitive sits in plaintext
- Loading secrets from 1Password, AWS, Azure, GCP, HashiCorp Vault, Infisical, Doppler, Bitwarden, and other providers via plugins
- Redacting secret values from logs and console output at runtime
- Giving AI coding agents full context on config (names, types, docs) without exposing secret values
- Running agents and MCP servers behind the varlock proxy so they only ever see placeholder credentials
- Scanning a repo for leaked secrets with `varlock scan`
Install:
```bash
npx varlock init # add to a JS/TS project
npm install varlock # or add the dependency directly
brew install dmno-dev/tap/varlock # standalone binary via Homebrew
curl -sSfL https://varlock.dev/install.sh | sh -s # standalone binary via script
```
Common CLI commands: `varlock init`, `varlock load`, `varlock run -- <cmd>`, `varlock encrypt`, `varlock scan`, `varlock proxy`.
Every page on varlock.dev can be fetched as markdown by sending an `Accept: text/markdown` header. The docs are also searchable over MCP at https://docs.mcp.varlock.dev/mcp (streamable HTTP) and https://docs.mcp.varlock.dev/sse.
## Documentation Sets
- [Abridged documentation](https://varlock.dev/llms-small.txt): a compact version of the documentation for Varlock, with non-essential content removed
- [Complete documentation](https://varlock.dev/llms-full.txt): the full documentation for Varlock
- [Getting started and CLI reference](https://varlock.dev/_llms-txt/getting-started-and-cli-reference.txt): installation, core concepts, env-spec syntax, decorators, and every CLI command
- [AI tools, MCP and proxy](https://varlock.dev/_llms-txt/ai-tools-mcp-and-proxy.txt): using varlock with coding agents, MCP servers, and the credential proxy
- [Framework and language integrations](https://varlock.dev/_llms-txt/framework-and-language-integrations.txt): Next.js, Vite, Astro, Bun, Python, Go, Rust, Java, PHP, Docker, CI, and more
- [Plugins](https://varlock.dev/_llms-txt/plugins.txt): 1Password, AWS, Azure, GCP, Vault, Infisical, Doppler, Bitwarden, Kubernetes, and other providers, plus Effect codegen
- [Sandboxes](https://varlock.dev/_llms-txt/sandboxes.txt): sandboxing recipes for running agents with the proxy
## Notes
- The complete documentation includes all content from the official documentation
- The content is automatically
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| 1password.dev | 1Password Developer Documentation | interface Developer tools APIs and SDKs +1 | — | 62 | ✓ | ✓ | |
| dotenvx.com | run every day at 8am | documentation Developer tools | — | 56 | ✓ | ✓ | |
| tembo.io | Tembo | interface Infrastructure AI and machine learning +2 | US | 54 | ✓ | ✓ | |
| infisical.com | Infisical | interface AI and machine learning Cybersecurity +1 | — | 63 | ✓ | ✓ | |
| chatgpt.com | Codex | documentation AI and machine learning Developer tools +1 | — | 72 | ✓ | ✓ | |
| enkryptai.com | Enkrypt AI | documentation AI and machine learning Cybersecurity +1 | US | 47 | ✓ | ||
| secretspec.dev | SecretSpec | documentation Cybersecurity Developer tools | — | 53 | ✓ | ✓ | |
| runloop.ai | Runloop | interface Developer tools AI agents and MCP +1 | US | 50 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=varlock.dev · GET /v1/domain/varlock.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage varlock.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for varlock.dev:
1. POST https://agentwebmap.com/v1/sites/varlock.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://varlock.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/varlock.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/varlock.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.