macOS
brew install wren-clilocal Homebrew formula metadata
sudo port install wren-cliMacPorts ports tree · lang/wren-cli/Portfile · Quelle: api.github.com
brew / Rang 9434
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für wren-cli in AI-Agent-Workflows.
Installation
brew install wren-clilocal Homebrew formula metadata
sudo port install wren-cliMacPorts ports tree · lang/wren-cli/Portfile · Quelle: api.github.com
Überblick
Simple REPL and CLI tool for running Wren scripts
Verlauf
Wren CLI is the standalone command-line companion to Wren, a small embeddable scripting language created by Bob Nystrom and later maintained in the wren-lang GitHub organization. The CLI exists because the core Wren VM is deliberately minimal: it gives users a REPL and script runner, plus operating-system-facing modules such as file I/O and networking that are intentionally not bundled into the language core.
In package-manager terms, wren-cli matters less as a large ecosystem tool and more as the practical executable that turns Wren from an embeddable VM into a shell-usable language runtime. It is the piece a developer installs when they want to run `.wren` scripts, experiment at a prompt, or study a small real-world embedding of the Wren VM.
The Wren language repository dates to 2013, and the language site describes Wren as a small, fast, class-based concurrent scripting language with an intentionally tiny implementation and standard library. In November 2018 Bob Nystrom announced that Sven Bergstrom, known as ruby0x1, would become Wren's lead maintainer and that the project would move under the `wren-lang` organization, preserving issues, pull requests, and project infrastructure.
The Wren development blog announced the maintainer transition publicly on 4 February 2019 and emphasized continuity: Wren would evolve while staying small, simple, learnable, and hackable. The separate `wren-cli` repository was created later in 2019 as the standalone command-line tool for the language, and GitHub releases show tagged CLI releases such as 0.3.0 in June 2020 and 0.4.0 in November 2021.
Wren's adoption has historically centered on embedding, games, language experimentation, and small tools rather than a large package ecosystem. The Wren homepage highlights the small VM and C API, while the CLI page frames wren-cli as both a practical tool and a real-world usage example for people learning how Wren can be embedded and extended.
The CLI also reflects Wren's post-2018 stewardship model: the language and supporting tools live in the shared `wren-lang` organization instead of only under the original author's account. That makes wren-cli part of the maintained Wren distribution story even though it is intentionally separate from the minimal core VM.
Users install or build `wren_cli` to run Wren source files, start a REPL, and access the CLI-specific modules documented at `wren.io/cli`. The CLI depends on libuv for operating-system features, which lets scripts use facilities such as file I/O and networking while keeping the base Wren language small.
Typical package-nerd usage is exploratory: run examples, test snippets, wire small scripts, or compare Wren's embedding model with Lua-style scripting. The CLI page is explicit that it is a work in progress and a standalone project, so users should treat it as the general-purpose executable around the language rather than as the entire Wren runtime.
wren-cli is significant because it packages the otherwise embeddable-first Wren VM into a normal Unix-style executable. That makes it indexable by Homebrew and MacPorts, scriptable from a shell, and easy to include in language-runtime inventories alongside Lua, Janet, or other compact embeddable languages.
Its separation from the core language is also historically interesting: Wren's design keeps the VM and standard library small, while the CLI carries the pragmatic I/O surface that package users expect from a runnable scripting language.
Sicherheitslage
generalized runtime or code generation signal.
yellow Risiko · mittel Konfidenz · runtime
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
wren_cli | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
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.
Installationsmetadaten
| Paketschlüssel | brew:wren-cli |
|---|---|
| Version | 0.4.0 |
| Paketmanager | Homebrew |
| Homepage | https://github.com/wren-lang/wren-cli |
| Repository | https://github.com/wren-lang/wren-cli |
| Zuletzt aktualisiert | 2026-07-10T09:59:34-04:00 |
| Pulse | updated |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Source-Datenbank-Treffer
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
wren-cli
sudo port install wren-cliQuellspur
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
View the package source record on GitHub.