# yeet mit Homebrew installieren

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

## Installation

```sh
sudo av install brew:yeet
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install yeet
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:yeet
- **Paketmanager:** Homebrew
- **Version:** 0.12.1
- **Quellzusammenfassung:** Packaging tool that lets you declare build instructions in JavaScript
- **Homepage:** <https://github.com/TecharoHQ/yeet>
- **Repository:** <https://github.com/TecharoHQ/yeet>
- **Zuletzt aktualisiert:** 2026-07-25T21:32:49+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- yeet (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

yeet is a Go-based packaging/build helper that runs small JavaScript `yeetfile.js` recipes. It targets the gap between shell scripts and full custom programs, with helpers for native packages, container operations, Git metadata, file installation, and language-specific build steps.

### Projektgeschichte

The TecharoHQ/yeet repository was created on 2025-03-28. Its README presents the project as a way to declare build instructions as small JavaScript snippets, with a first-class `yeetfile.js` example that builds a Go program into an RPM.

The API documentation explains a deliberate design boundary: yeet executes JavaScript with goja, does not provide npm access, and does not allow importing code or data from other files. Reusable functionality is expected to become a native yeet interface instead of a local JavaScript dependency tree.

The tool evolved around practical packaging helpers: `deb`, `rpm`, and `tarball`-style native package builders, systemd extension and portable-service images, Docker aliases, Git helpers, file helpers, Go build helpers, and package upload integrations.

### Adoptionsgeschichte

Yeet is a young, niche tool, so adoption evidence is necessarily light. Its README links a Repology packaging-status badge, pkg.go.dev indexes the Go module, Homebrew packages the command, and Techaro discussions mention using yeet while testing Techaro apt/rpm repository definitions.

Its likely adopters are maintainers of Go or mixed-language projects who want packaging recipes to stay close to source without writing full RPM spec/deb-helper machinery by hand for every simple artifact.

### Wie es verwendet wird

A project adds a `yeetfile.js` and calls helpers such as `rpm.build` or `deb.build` with descriptor objects. The build callback can invoke shell commands with the `$` tagged-template helper and place compiled output in the package layout paths supplied by yeet.

The API docs also show uses beyond simple packages: building systemd configuration extensions, system extensions, portable service images, Docker images, copying files while preserving modes, reading Git tags, and uploading binary packages to Gitea-backed repositories.

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

Yeet is package-nerd significant because it is packaging tooling about package production itself. It tries to make native artifacts scriptable while avoiding the full dependency sprawl of a JavaScript toolchain.

Its no-import/no-npm rule is also notable: for packaging, fewer moving parts can be a feature. The project bakes common packaging operations into Go-backed helpers and leaves the recipe file as a compact declaration of what to build.

### Zeitleiste

- 2025-03-28: The TecharoHQ/yeet repository is created.
- 2025: The README documents `yeetfile.js` recipes and native package examples.
- 2025: The API documentation covers helpers for Debian packages, RPM packages, tarballs, Docker, Git, files, Go builds, Gitea uploads, and systemd image formats.
- 2025-05-26: A Techaro Anubis discussion references a proof-of-concept apt/rpm repository for testing packages including yeet.

### Related projects

- Related projects and technologies include goja, RPM packaging, Debian packaging, systemd portable services, systemd system extensions, Docker, Gitea package registries, Go build tooling, npm scripts, Make, goreleaser, nfpm, and project-local build recipes.

### Quellen

- <https://api.github.com/repos/TecharoHQ/yeet>
- <https://formulae.brew.sh/formula/yeet>
- <https://github.com/TecharoHQ/anubis/discussions/567>
- <https://github.com/TecharoHQ/yeet>
- <https://pkg.go.dev/github.com/TecharoHQ/yeet>
- <https://raw.githubusercontent.com/TecharoHQ/yeet/main/README.md>
- <https://raw.githubusercontent.com/TecharoHQ/yeet/main/doc/api.md>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## 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

- Unix: yeetfile.js

## Combined YAML source

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


## Quellen

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