# luvit mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:luvit
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install luvit
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:luvit
- **Paketmanager:** Homebrew
- **Version:** 2.18.1
- **Quellzusammenfassung:** Asynchronous I/O for Lua
- **Homepage:** <https://luvit.io>
- **Repository:** <https://github.com/luvit/luvit>
- **Zuletzt aktualisiert:** 2026-08-02T05:25:43Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- luvi (Alias)
- luvit (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 2.18.1
## Projektgeschichte und Nutzung

Luvit is a LuaJIT runtime and package ecosystem that brings Node.js-style asynchronous programming to Lua through libuv, luvi, and lit. It is packaged as both a scripting command and a library-oriented runtime for small servers, tools, and bundled Lua applications.

### Projektgeschichte

The public Luvit repository was created in September 2011 and describes the project as combining Lua, libUV, and LuaJIT. Its 2.0 README explains that the repository became a metapackage containing the luvit/luvit package plus the luvit/* packages published to lit, with luvi providing the executable runtime layer.

The official site presents Luvit as 'Asynchronous I/O for Lua' and emphasizes a familiar Node.js-like API, coroutine-friendly asynchronous styles, and a modular core where luv, luvi, lit, and the Node-style packages can be mixed as needed.

### Adoptionsgeschichte

Luvit has remained a niche but recognizable runtime in Lua package-manager culture. The official repository had about 4,000 stars and 375 forks in July 2026, and its documented support channels include GitHub issues, Discord, and the mailing list.

The project is also a useful historical bridge between the Node.js/libuv world and Lua: it made libuv-style event loops and npm-like package workflows available to Lua users before those ideas were common in the wider Lua ecosystem.

### Wie es verwendet wird

The `luvit` CLI runs Lua scripts as standalone servers, clients, and tools. The official homepage shows a small HTTP server launched with `luvit server.lua`, and the README documents using `make`, `luvi .`, and `make test` for core development.

Third-party packages are installed through lit, for example `lit install creationix/weblit`, and Luvit packages are usually written against Node-like APIs such as `http` while still allowing coroutine-based styles.

### Warum Paket-Nerds sich dafür interessieren

Luvit matters because it is not just a Lua library: it is a runtime, package manager culture, and bundling story in one small ecosystem. For package maintainers, it represents the class of language runtimes that pull in a native event loop, a custom package manager, and a language-specific executable.

### Zeitleiste

- 2011: Public `luvit/luvit` repository created on GitHub.
- 2015-2018: Luvit homepage era documenting the luvi/lit/luv ecosystem.
- 2020: Luvit 2.17.0 release published.
- 2021: Luvit 2.18.1 release published.

### Related projects

- luvi provides the base executable runtime used to run bundled Luvit applications.
- lit is the package manager and package database used by the Luvit ecosystem.
- luv provides Lua bindings to libuv and can be used outside Luvit.

### Quellen

- <https://api.github.com/repos/luvit/luvit>
- <https://api.github.com/repos/luvit/luvit/releases?per_page=5>
- <https://github.com/luvit/luvit#readme>
- <https://luvit.io/>
- <https://luvit.io/docs.html>


## Sicherheitshinweise

broad file, network, media, or database tool signal.

- **Geiger-Risiko:** blue / mittel
- broad file, network, media, or database tool signal


## Combined YAML source

View the package source record on GitHub. [combined/luvit.yml](https://github.com/mxcl/pkgdb/blob/main/combined/luvit.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph
