install

Additional install commands

macOS

Homebrewverified · 100%

brew install static-web-server

local Homebrew formula metadata

Linux

Nixverified · 92%

nix profile install nixpkgs#static-web-server

nixpkgs package indexes · pkgs/by-name/st/static-web-server/package.nix · source: api.github.com

Windows

Scoopverified · 92%

scoop install main/static-web-server

Scoop official bucket manifest trees · bucket/static-web-server.json · source: api.github.com

overview

Package summary

High-performance and asynchronous web server for static files-serving

Project links

Commands and aliases

static-web-server

history

Project history and usage

Static Web Server is a Rust command-line HTTP server for serving static files and assets. In package-manager culture it belongs to the small, single-purpose server family: a binary that can be installed quickly, pointed at a directory, and used for local previews, containers, CI jobs, or simple production static hosting.

Project history

The upstream repository was created in September 2019 and the project describes itself as a cross-platform, high-performance asynchronous static-file server. Its README emphasizes a tiny production-ready server built on Rust, Hyper, and Tokio, with HTTP/1, HTTP/2, TLS, compression, directory listings, cache headers, CORS, and other deployment-oriented features.

The project moved beyond a local preview utility by publishing release binaries, Docker images, a crates.io package, and official documentation. The v2 series is documented as the stable line while the main branch README identifies an upcoming v3 as still in development.

Adoption history

The input package metadata lists Static Web Server in Homebrew, Nix, and Scoop, which places it in the cross-platform CLI packaging set used by developers on macOS, Linux, and Windows. The official README also highlights prebuilt binaries, Docker images, crates.io, docs.rs, and support for Linux, macOS, Windows, FreeBSD, NetBSD, Android, Docker, and WebAssembly.

Its adoption pattern is typical for Rust infrastructure CLIs: package managers provide the executable for day-to-day use, while Docker and static release binaries cover container and server deployments.

How it is used

Common usage is to install the `static-web-server` executable and serve a directory of static content. Configuration can be supplied through command-line flags, environment variables, or a TOML file, making the tool convenient both for one-off local serving and repeatable deployment.

Why package nerds care

Package maintainers care about Static Web Server because it is a modern replacement for ad hoc `python -m http.server` style workflows when users need compression, TLS, headers, logging, Docker images, and static binaries without bringing in a full application server.

Its value in package indexes comes from being a small executable with a large practical surface: easy to bottle or cache, useful in CI, and relevant to web projects that only need to ship files.

Timeline

2019: Upstream GitHub repository created.
2019: Early v1 release series published on GitHub.
2026: Official downloads page listed v2.43.0 with release binaries for multiple platforms.

Related projects

Related tools include other static-file servers and development preview servers, while the implementation is tied to the Rust Hyper and Tokio ecosystem.

Sources

https://github.com/static-web-server/static-web-server
https://raw.githubusercontent.com/static-web-server/static-web-server/master/README.md
https://static-web-server.net/download-and-install/
input.source_facts.package-manager
input.source_facts.repo

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:sync,server

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: ./sws.toml
Windows: .\sws.toml

executables

Installed executables

Command	Kind	Exposure	Note
`static-web-server`	cli	global 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-07-08

manager version2.43.0

manager updated2026-06-10

local dataok

upstreamcurrent

latest detectedv2.43.0

https://github.com/static-web-server/static-web-server

okNo freshness warnings were generated.

install metadata

Package metadata

Package key	brew:static-web-server
Version	2.43.0
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/static-web-server
Homepage	https://static-web-server.net
Repository	https://github.com/static-web-server/static-web-server
Upstream docs	https://static-web-server.net/
License	Apache-2.0 OR MIT
Source archive	https://github.com/static-web-server/static-web-server/archive/refs/tags/v2.43.0.tar.gz
Last updated	2026-06-10T22:07:37Z
Pulse	updated
Build dependencies	rust
Bottle	available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	static-web-server
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
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%

static-web-server

nix profile install nixpkgs#static-web-server

normalized package name match
Matched by: Static Web Server

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

Scoop95%

main/static-web-server

scoop install main/static-web-server

normalized package name match
Matched by: Static Web Server

Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/static-web-server.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

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.

Combined YAML source

View the package source record on GitHub.

combined/static-web-server.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
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

Install static-web-server with Homebrew, Nix, scoop