pkg.soopen package index

brew / Rang 2298

posting mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install posting

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#posting

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

Überblick

Paketzusammenfassung

Modern API client that lives in your terminal

Befehle und Aliase

  • posting

Verlauf

Projektgeschichte und Nutzung

Posting is a keyboard-oriented terminal UI for creating, organizing, sending, and inspecting HTTP and API requests.

Projektgeschichte

Darren Burns created Posting as a terminal HTTP client using Python and the Textual interface framework. The 2.x line expanded collections, scripting, OpenAPI import, themes, authentication, and persisted history.

In 2026 the project announced Posting 3, a Go rewrite distributed as a single binary while retaining compatibility with existing Posting 2 collections and configuration.

Adoptionsgeschichte

Posting is distributed through Homebrew and project releases and stores requests as readable YAML files, making collections suitable for version control and team exchange. Its documentation also describes importing Postman collections and curl commands.

Posting 3 preserves Posting 2 configuration and collection compatibility while moving to a self-contained binary distribution.

Wie es verwendet wird

Users compose HTTP requests interactively, organize `.posting.yaml` request files into collection directories, switch variable environments, inspect responses, and import or export curl commands.

The configuration path can be printed with `posting locate config`; its documented default is `$XDG_CONFIG_HOME/posting/config.yaml`, normally `~/.config/posting/config.yaml`. Environment files and request files may contain secrets, but they are user-selected project files rather than a fixed credentials file. Posting 3 stores OAuth tokens in the operating system credential store when available.

Warum Paket-Nerds sich dafür interessieren

Posting brings a graphical API-client workflow into a terminal-native TUI: request editing, collections, environments, authentication, response inspection, history, and keyboard navigation remain available without leaving the shell.

Its plain YAML request format and curl import/export make it attractive to users who want inspectable, version-controlled API fixtures rather than an opaque desktop-client database.

Zeitleiste

  • 2024: Posting 2.0 added pre-request and post-request scripting.
  • 2026: Posting 2.11 added persisted request-and-response history.
  • 2026: Posting 3 began a Go-based single-binary generation while retaining collection compatibility.

Related projects

  • curl commands can be imported into Posting and Posting requests can be exported back to curl.
  • Postman collection files can be imported into Posting.

Sicherheitslage

Risikostufe: blue

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

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

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

Signale

  • text:client

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 5 Plattformziele verfügbar.
  • Installiert mit 6 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 2 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
config.yaml (see `posting locate config`)

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
postingcliglobales 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-11-04
Manager-Version2.11.2
Manager aktualisiert2026-10-24
lokale DatenOK
Upstreamaktuell
neueste erkannte Version2.11.2

https://github.com/darrenburns/posting

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:posting
Version2.11.2
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/posting
Homepagehttps://github.com/darrenburns/posting
Repositoryhttps://github.com/darrenburns/posting
LizenzApache-2.0
Quellarchivhttps://github.com/darrenburns/posting/archive/refs/tags/2.11.2.tar.gz
Zuletzt aktualisiert2026-10-24T12:07:47Z
Pulseupdated
Abhängigkeitenbrotli, certifi, libyaml, pydantic, python@3.15, tree-sitter
Build-Abhängigkeitencmake, rust
Bottleverfügbar (auf arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameposting
Version Scheme0
Revision1
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

posting

nix profile install nixpkgs#posting
  • normalized package name match
  • Abgeglichen nach: Posting
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/po/posting/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

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
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkg.so package database
  • pkgdb category and tag curation