Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install static-web-server

local Homebrew formula metadata

Linux

Nixverifiziert · 92%

nix profile install nixpkgs#static-web-server

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

Windows

Scoopverifiziert · 92%

scoop install main/static-web-server

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

Überblick

Paketzusammenfassung

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

Projektlinks

Befehle und Aliase

static-web-server

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

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.

Quellen

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

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

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
Build-Metadaten listen 1 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: ./sws.toml
Windows: .\sws.toml

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit	Hinweis
`static-web-server`	cli	globales 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-07-25

Manager-Version2.43.0

Manager aktualisiert2026-06-10

lokale DatenOK

Upstreamaktuell

neueste erkannte Versionv2.43.0

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

OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:static-web-server
Version	2.43.0
Paketmanager	Homebrew
Paketmanager-Seite	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-Dokumentation	https://static-web-server.net/
Lizenz	Apache-2.0 OR MIT
Quellarchiv	https://github.com/static-web-server/static-web-server/archive/refs/tags/v2.43.0.tar.gz
Zuletzt aktualisiert	2026-06-10T22:07:37Z
Pulse	updated
Build-Abhängigkeiten	rust
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

static-web-server

nix profile install nixpkgs#static-web-server

normalized package name match
Abgeglichen nach: 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
Abgeglichen nach: 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

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

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.

Combined YAML source

View the package source record on GitHub.

combined/static-web-server.yml

Verwendete Quellen

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

static-web-server mit Homebrew, Nix, scoop installieren