andrew-d/static-binaries

Analysis updated 2026-07-03

★ 3,687ShellAudience · ops devopsComplexity · 2/5Setup · easy

Mindmap

mindmap
  root((static-binaries))
    What it does
      Pre-built tools
      No install required
      Single file deploy
    Tools included
      nmap port scanner
      tcpdump
      strace
      nano ag socat
    How it works
      Docker build scripts
      Per-tool Dockerfile
      Output folder
    Use cases
      Server deployment
      Container tooling
      Security testing

mindmap root((static-binaries)) What it does Pre-built tools No install required Single file deploy Tools included nmap port scanner tcpdump strace nano ag socat How it works Docker build scripts Per-tool Dockerfile Output folder Use cases Server deployment Container tooling Security testing

Click or tap to explore — scroll the page freely

What do people build with it?

USE CASE 1

Drop a static nmap binary onto a server or container to scan for open ports without installing any packages.

USE CASE 2

Use a static strace binary on a production Linux server to trace system calls for debugging without touching the package manager.

USE CASE 3

Build your own static binary of a tool you need by cloning the repo, adding a Dockerfile for it, and running the Docker build.

USE CASE 4

Copy a static tcpdump binary into a minimal Docker container to capture network traffic for debugging without adding dependencies.

What is it built with?

ShellDockerC

How does it compare?

	andrew-d/static-binaries	olegos2/mobox	xtls/xray-examples
Stars	3,687	3,700	3,673
Language	Shell	Shell	Shell
Setup difficulty	easy	hard	hard
Complexity	2/5	4/5	3/5
Audience	ops devops	general	ops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Download the pre-built binary directly, no compilation needed unless you want to build a new tool, which requires Docker.

No license file mentioned, usage terms are unclear, use at your own discretion.

In plain English

This repository is a collection of pre-built command-line tools compiled as static binaries for Linux and other Unix-like systems. A static binary packages everything the program needs into a single file, so it can run on a machine without requiring any additional libraries to be installed. This makes it useful for deploying tools onto servers, containers, or restricted environments where you cannot or do not want to install software through a package manager. The tools available include network utilities such as nmap (a port scanner) and tcpdump (a network traffic capture tool), text tools like nano (a terminal text editor) and ag (a fast file search tool), and system utilities like strace (which traces system calls a program makes) and socat (a networking relay). Python and several other tools are also included. Each tool has its own subdirectory containing a Dockerfile and build scripts. Running the Docker build produces the compiled binary, which gets placed in a shared output folder. The README notes that not every tool is available for every processor architecture, and some tools have quirks: the static Python build requires a specific flag and a zip file containing the standard library, and the file tool needs to be pointed at a bundled magic database file to work correctly. The project was built by one person as tools were needed, rather than as a comprehensive suite. New tool requests can be filed as GitHub issues. There is no license file mentioned in the README. The repository is primarily useful for system administrators, security researchers, and developers who need a reliable, portable copy of a Unix tool without installing anything.

Copy-paste prompts

Prompt 1

I need to run nmap on a locked-down Linux server where I can't install packages. Show me how to download the static binary from andrew-d/static-binaries and use it to scan a subnet.

Prompt 2

Help me add a new tool to the andrew-d/static-binaries repo by creating a Dockerfile that compiles it as a static binary and outputs it to the shared folder.

Prompt 3

I want to use the static Python binary from this repo. What is the specific flag and zip file I need to make it work correctly?

Prompt 4

Walk me through using the static socat binary to set up a simple TCP relay between two ports on a Linux machine with no package manager access.

Prompt 5

How do I build all the static binaries in andrew-d/static-binaries locally using Docker, and where do the compiled files end up?

Frequently asked questions

What is static-binaries?

A collection of pre-built static Linux binaries (nmap, tcpdump, strace, Python, and more) that run on any machine without installing libraries or using a package manager.

What language is static-binaries written in?

Mainly Shell. The stack also includes Shell, Docker, C.

What license does static-binaries use?

No license file mentioned, usage terms are unclear, use at your own discretion.

How hard is static-binaries to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is static-binaries for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub andrew-d on gitmyhub

Verify against the repo before relying on details.