pkg.soopen package index

brew / rank 2298

Install posting with Homebrew, Nix

Modern API client that lives in your terminal. Version 2.11.2 via Homebrew; verified 2026-10-24. Also installable with nix: nix profile install nixpkgs#posting.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install posting

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#posting

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

overview

Package summary

Modern API client that lives in your terminal

Commands and aliases

  • posting

history

Project history and usage

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

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

  • 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.

security posture

Risk level: blue

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

Risk classifier

blue risk · medium confidence · tool

Why

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

Signals

  • text:client

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 5 platform targets.
  • Installs with 6 runtime dependencies.
  • Build metadata lists 2 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

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

Installed executables

CommandKindExposureNote
postingcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-11-04
manager version2.11.2
manager updated2026-10-24
local dataok
upstreamcurrent
latest detected2.11.2

https://github.com/darrenburns/posting

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:posting
Version2.11.2
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/posting
Homepagehttps://github.com/darrenburns/posting
Repositoryhttps://github.com/darrenburns/posting
LicenseApache-2.0
Source archivehttps://github.com/darrenburns/posting/archive/refs/tags/2.11.2.tar.gz
Last updated2026-10-24T12:07:47Z
Pulseupdated
Dependenciesbrotli, certifi, libyaml, pydantic, python@3.15, tree-sitter
Build dependenciescmake, rust
Bottleavailable (on arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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 database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

posting

nix profile install nixpkgs#posting
  • normalized package name match
  • Matched by: 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

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • 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