brew / Rang 7204

wtf mit Homebrew, MacPorts, Nix installieren

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

Installationsbefehl Sicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install wtf

local Homebrew formula metadata

MacPortsverifiziert · 94%

sudo port install wtf

MacPorts ports tree · games/wtf/Portfile · Quelle: api.github.com

Linux

Nixverifiziert · 92%

nix profile install nixpkgs#wtf

nixpkgs package indexes · pkgs/by-name/wt/wtf/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Translate common Internet acronyms

Projektlinks

Homepage

Befehle und Aliase

Verlauf

Projektgeschichte und Nutzung

wtf is the small BSD command-line acronym lookup utility: users type forms such as `wtf TCP` or the natural-language `wtf is TCP`, and the command expands matching terms from acronym databases or falls back to system help sources.

Projektgeschichte

The current NetBSD manual identifies `wtf` as a section 6 utility that looks up one or more terms, first in acronym databases and then through tools such as whatis, pkg_info, and pkgsrc help when appropriate. Its files include the default acronym database, an offensive acronym database enabled by option, and a computer-related acronym database.

The FreeBSD 7.2 manual page records the historical origin succinctly: `wtf` first appeared in NetBSD 1.5. The current NetBSD manual adds that it initially only translated acronyms, while later versions gained the ability to look up terms in other system sources.

Adoptionsgeschichte

The command spread beyond NetBSD through BSD ports and redistributions of the NetBSD script and acronym databases. The SourceForge bsd-wtf project describes itself as a convenient place to get the `wtf` program and acronyms database outside the NetBSD source tree, while FreeBSD and other packaging ecosystems carried variants for users who wanted the BSD utility on non-NetBSD systems.

Wie es verwendet wird

The canonical usage is intentionally casual: `wtf` accepts an optional ignored `is` operand so `wtf is WTF` works naturally. Users can override the acronym database with `-f` or the ACRONYMDB environment variable, which makes the tool easy to adapt to local jargon lists.

In pkgsrc-aware environments, the command is more than a slang lookup: if an acronym is not found, it can ask package and manual-page sources. That makes it a tiny bridge between Unix wordplay, system documentation, and package-tree help.

Warum Paket-Nerds sich dafür interessieren

wtf is package-nerd lore because it is a deliberately unserious command that still follows Unix conventions: plain text databases, environment overrides, manpage documentation, and integration with package metadata. It is also a reminder that BSD games and misc utilities often became portable command-line packages in their own right.

Zeitleiste

2000: NetBSD 1.5 era in which `wtf` first appeared.
2007-07-27: The FreeBSD 7.2 manual page documents the NetBSD origin.
2015-04-22: The current NetBSD manual page documents later term-lookup behavior beyond acronym translation.
2010s: SourceForge bsd-wtf provides the NetBSD utility and acronym database outside the NetBSD source tree.

Related projects

NetBSD supplies the canonical manual page and acronym database behavior.
SourceForge bsd-wtf mirrors the NetBSD utility and data for use outside the NetBSD tree.
FreeBSD carried a ported manual page documenting the NetBSD origin.

Quellen

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

Es wurden keine Homebrew-Bottle-Metadaten erfasst.

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.

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit	Hinweis
`wtf`	Executable	indexiertes Executable	Aus dem lokalen Executable-Index erkannt.

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-08-03

Manager-Version20230906

Manager aktualisiert

lokale Datenunbekannt

Upstreamnicht verfügbar

neueste erkannte Versionnicht erkannt

OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:wtf
Version	20230906
Paketmanager	Homebrew
Homepage	https://sourceforge.net/projects/bsdwtf/
Bottle	nicht erfasst
Dienst	keiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

wtf

nix profile install nixpkgs#wtf

normalized package name match
Abgeglichen nach: Wtf

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/wt/wtf/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

MacPorts95%