pkg.soopen package index

brew / rank 7959

Install red-tldr with Homebrew

Used to help red team staff quickly find the commands and key points. Version 0.5.0 via Homebrew; verified 2026-09-13.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install red-tldr

local Homebrew formula metadata

overview

Package summary

Used to help red team staff quickly find the commands and key points

Commands and aliases

  • red-tldr

history

Project history and usage

Red Team TL;DR is an offline-first command and technique lookup tool for experienced red-team operators. It combines fuzzy full-text search over a curated YAML database with structured output, MITRE ATT&CK metadata, and an optional MCP server.

Project history

red-tldr began as a lightweight lookup tool for experienced red-team operators who remember fragments of commands but need fast access to exact syntax and operational notes. It uses a curated, locally searchable database rather than general web search.

The project later added Bleve-powered full-text and fuzzy search, structured text, JSON, and Markdown output, richer entries with MITRE ATT&CK mappings, and an independently maintained red-tldr-db repository.

Version 0.5.0 introduced a built-in Model Context Protocol server supporting both standard input/output and Streamable HTTP transports.

Adoption history

red-tldr is available through Homebrew on macOS, the Arch User Repository, downloadable release archives, and source builds. Its offline-first design avoids cloud or API-key dependencies.

From version 0.5.0, the project broadened its audience beyond direct terminal use by embedding an MCP server for AI assistants such as Claude Desktop and Cursor.

How it is used

Operators search using a complete keyword or a remembered fragment and choose among ranked matches. Results can be printed for terminal reading or emitted as JSON or Markdown.

The update command rebuilds the local search index, while upgrade downloads the latest database from GitHub. The serve command exposes the knowledge base to MCP clients over stdio or Streamable HTTP.

The default configuration at ~/.red-tldr/config.toml controls automatic index rebuilding, database downloads, the database storage path, and colored output. No API credentials are required.

Why package nerds care

red-tldr packages an operator-maintained offensive-security knowledge base behind a fast local CLI. Its separation of the search program from a YAML database, deterministic offline behavior, structured output, and built-in MCP endpoint make it an unusual bridge between traditional command cheat sheets and agent-accessible security references.

Timeline

  • Initial project: Introduced a lightweight local lookup tool for red-team commands and key operational notes.
  • Version 0.5.0: Added an MCP server and an enhanced, backward-compatible data model.
  • Current packaging: Distributed through Homebrew, AUR, release binaries, and source builds.

Related projects

  • red-tldr-db is the companion repository containing the YAML knowledge-base entries searched by the client.
  • The project's concise command-reference model is conceptually related to tldr pages, but it is specialized for offensive-security commands and experienced red-team workflows.

Sources

  • Companion database linked by the official README: https://github.com/Rvn0xsy/red-tldr-db
  • Official project site: https://payloads.online/red-tldr
  • Official repository and README: https://github.com/Rvn0xsy/red-tldr
  • Package availability: source_facts.package-manager

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 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
~/.red-tldr/config.toml

executables

Installed executables

CommandKindExposureNote
red-tldrcliglobal 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-09-19
manager version0.5.0
manager updated2026-09-13
local dataok
upstreamcurrent
latest detectedv0.5.0

https://github.com/Rvn0xsy/red-tldr

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:red-tldr
Version0.5.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/red-tldr
Homepagehttps://payloads.online/red-tldr/
Repositoryhttps://github.com/Rvn0xsy/red-tldr
Upstream docshttps://payloads.online/red-tldr/
LicenseMIT
Source archivehttps://github.com/Rvn0xsy/red-tldr/archive/refs/tags/v0.5.0.tar.gz
Last updated2026-09-13T07:31:51Z
Pulseupdated
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

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
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkg.so package database
  • pkgdb category and tag curation