Automic VaultAutomic Vault

brew

varlock mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für varlock in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install varlock

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Add declarative schema to .env files using @env-spec decorator comments

Verlauf

Projektgeschichte und Nutzung

Varlock is a young configuration and secrets tool for `.env`-based workflows. Its project tagline frames the tool around AI-safe `.env` files: schemas are safe for agents and collaborators to read, while actual secrets are resolved separately.

Projektgeschichte

The project is built on `@env-spec`, a DSL that extends normal `.env` syntax with JSDoc-style decorator comments and function-call values. The initial `@env-spec` RFC was proposed on May 13, 2025 by maintainers Phil Millman and Theo Ephraim, describing the goal of richer validation, type coercion, sensitive-value handling, and dynamic loading while keeping the familiar `.env` format.

Adoptionsgeschichte

Varlock targets the pain point left by `.env.example`: example files are safe to commit but often drift from real runtime requirements. Varlock instead promotes a committed `.env.schema` as a single source of truth, with local or environment-specific `.env.*` files supplying values.

Wie es verwendet wird

Typical usage starts with `varlock init`, which scans existing `.env` files and creates a root `.env.schema`. Users then run `varlock load` to validate and inspect resolved environment variables or `varlock run -- <command>` to execute a process with resolved values. The tool also ships as a standalone binary, Docker image, editor support, and plugins for secret backends such as 1Password, AWS, Azure, Google Secret Manager, HashiCorp Vault, and others.

Warum Paket-Nerds sich dafür interessieren

For package users, Varlock is notable as an attempt to standardize metadata around environment variables without forcing a new YAML, JSON, or TypeScript schema file. It is especially tuned for modern AI-assisted development, where agents need configuration context but should not be handed plaintext secrets.

Zeitleiste

  • 2025-05-13: Initial `@env-spec` RFC proposed.
  • 2026: Repository documents Varlock as a CLI, Docker image, VS Code extension ecosystem, and plugin host for multiple secret backends.

Related projects

  • DMNO is cited by the maintainers as the predecessor whose lessons informed Varlock.
  • `@env-spec` is the underlying specification and parser family used by Varlock.

Quellen

  • Initial @env-spec RFC: https://github.com/dmno-dev/varlock/discussions/17
  • Official @env-spec overview: https://varlock.dev/env-spec/overview/
  • Official GitHub repository: https://github.com/dmno-dev/varlock
  • Official installation guide: https://varlock.dev/getting-started/installation/

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für varlock wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
.env.schema

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
.env.local.env.*

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
varlockcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version1.13.0
Manager aktualisiert2026-07-22
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://varlock.dev

  • InfoRelease/tag comparison is only available for GitHub repositories.https://varlock.devnone Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:varlock
Version1.13.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/varlock
Homepagehttps://varlock.dev
Repositoryhttps://github.com/dmno-dev/varlock
Upstream-Dokumentationhttps://varlock.dev/getting-started/introduction
LizenzMIT
Quellarchivhttps://registry.npmjs.org/varlock/-/varlock-1.13.0.tgz
Zuletzt aktualisiert2026-07-22T21:21:52Z
Pulseupdated
Abhängigkeitennode
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namevarlock
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment