Automic VaultAutomic Vault

brew

envd mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install envd

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Reproducible development environment for AI/ML

Verlauf

Projektgeschichte und Nutzung

envd is TensorChord's command-line tool for creating container-based development environments for AI and machine-learning work. It uses a Python-like `build.envd` declaration to turn Python, CUDA, shell, Jupyter, and container setup into a repeatable environment.

Projektgeschichte

The README presents envd as a reaction to fragile AI/ML development setups, where Python packages, CUDA, shell scripts, and Dockerfiles often break together. Its core promise is to replace hand-written environment assembly with a simple declaration plus `envd up`.

The project builds OCI-compatible images and uses technologies such as Docker and BuildKit. Its documentation also covers local and Kubernetes-backed contexts, remote builds, package caches, Jupyter setup, and reusable build functions imported from Git repositories.

Adoptionsgeschichte

envd is distributed through several developer channels: the README documents pip installation, direct GitHub release binaries, and bootstrap after installation, while Homebrew packages it as `envd`. Homebrew analytics showed low hundreds of annual installs during this run, consistent with a specialized AI/ML infrastructure tool.

Wie es verwendet wird

A typical workflow installs envd, runs `envd bootstrap`, creates or clones a project with a `build.envd` file, and runs `envd up` to build and attach to the containerized environment. The example manifest installs conda, Python, Python packages, a shell, and optional Jupyter support.

The package is especially relevant where reproducibility and GPU/container setup matter: local notebooks, remote build machines, Kubernetes clusters, and teams sharing environment definitions.

Warum Paket-Nerds sich dafür interessieren

envd is a packaging-adjacent tool because it treats development environments themselves as declarative artifacts. For package nerds, it sits at the intersection of language package managers, OCI images, BuildKit caching, and reproducible developer onboarding.

Zeitleiste

  • 2022: TensorChord copyright and envd documentation identify the project era.
  • 2020s: envd documents pip, release-binary, and Homebrew installation paths.
  • 2020s: envd expands beyond local containers with remote build, cache, and Kubernetes-oriented documentation.

Related projects

  • envd builds on Docker, BuildKit, OCI images, conda, Python packaging, Jupyter, and Kubernetes.
  • envdlib is documented as a reusable library of envd build functions imported from Git repositories.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhä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
build.envd

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
envdcliglobales 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-08
Manager-Version1.3.4
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.3.4

https://github.com/tensorchord/envd

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:envd
Version1.3.4
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/envd
Homepagehttps://envd.tensorchord.ai
Repositoryhttps://github.com/tensorchord/envd
Upstream-Dokumentationhttps://envd.tensorchord.ai/guide/getting-started
LizenzApache-2.0
Quellarchivhttps://github.com/tensorchord/envd/archive/refs/tags/v1.3.4.tar.gz
Build-Abhängigkeitengo
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 Nameenvd
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • 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