# h2spec mit Homebrew, Nix installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für h2spec in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:h2spec ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install h2spec ``` Evidenz: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#h2spec ``` Evidenz: nixpkgs package indexes: pkgs/by-name/h2/h2spec/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Paketfakten - **Paketschlüssel:** brew:h2spec - **Paketmanager:** Homebrew - **Paketmanager-Seite:** - **Version:** 2.6.0 - **Quellzusammenfassung:** Conformance testing tool for HTTP/2 implementation - **Homepage:** - **Repository:** - **Upstream-Dokumentation:** - **Lizenz:** MIT - **Quellarchiv:** - **Generiert:** 2026-07-08T18:08:21+00:00 ## Executables - h2spec (cli) - h2spec (Alias) ## Build-Abhängigkeiten - go ## Installationsverhalten - Post-install-Hook: nicht definiert - Bottle: verfügbar auf arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, monterey, sonoma, ventura ## Version und Aktualität - Seite generiert: 2026-07-08 - Manager-Version: 2.6.0 - lokale Daten: OK - Upstream-Repository: https://github.com/summerwind/h2spec - Info: No package-manager update timestamp was available. - Info: No cached GitHub release or tag data was available. ## Projektgeschichte und Nutzung h2spec is a Go command-line conformance tester for HTTP/2 implementations. It became a standard developer tool because it translates the protocol rules in RFC 7540 and HPACK rules in RFC 7541 into runnable test cases against real servers. ### Projektgeschichte The repository was created in August 2014, during the final stretch of HTTP/2 standardization. The first GitHub release, v0.0.1, was published in December 2014 as an alpha release, and rapid 0.0.x releases followed with TLS, stream-state, frame, and timeout test coverage. Version 1.0.0 was published in May 2015, shortly after the publication of RFC 7540 and RFC 7541. Later 1.x releases added HPACK-related tests, section-specific checks, JUnit reporting, performance improvements, and more detailed error handling. Version 2.0.0 in January 2017 refactored the test cases, added RFC 7541 HPACK tests, added HTTP/2 server tests, dry-run mode, individual test-case execution, and verbose logging. Subsequent 2.x releases tracked Go toolchain changes and fixed conformance details around GOAWAY, frame lengths, HPACK strings, path selection, and TLS cipher selection. ### Adoptionsgeschichte h2spec's adoption came from implementers needing an independent executable check for HTTP/2 behavior. The 2015 HTTP Workshop presentation by Moto Ishizawa described the goal as sharing test cases because HTTP/2 implementations are hard to test. The tool appears in official and community workflows for server and library validation because it can be installed as a binary, run from Docker, or built from source. Homebrew and Nix packaging made it easy to use in local development and CI jobs. ### Wie es verwendet wird h2spec targets a host and port, optionally over TLS, and can run the entire suite or a single spec section such as `http2/6.3`. Its supported spec IDs include `http2`, `hpack`, and `generic`, and it offers strict mode for SHOULD-level requirements plus JUnit output for CI reporting. Package users typically run it against a local web server, proxy, HTTP/2 library example server, or appliance endpoint to catch protocol-state, frame-format, stream, HPACK, or error-handling mistakes. ### Warum Paket-Nerds sich dafür interessieren h2spec matters because it turned an RFC-reading task into a repeatable CLI check. For package maintainers, it is a small but high-leverage tool: it can validate HTTP/2 support in servers such as H2O, HAProxy, nginx builds, language libraries, and reverse proxies without embedding a full benchmark or browser stack. Its release history is also a useful map of HTTP/2 implementation pain points: stream states, SETTINGS, GOAWAY, HPACK, TLS, headers, padding, and CI-friendly reporting all show up as packageable conformance concerns. ### Zeitleiste - 2014: Repository created and v0.0.1 alpha released. - 2015: v1.0.0 released after HTTP/2 and HPACK RFC publication. - 2015: HTTP Workshop presentation described h2spec as a shared conformance-test tool. - 2017: v2.0.0 refactored test cases and added HPACK, dry-run, and individual-test execution. - 2020: v2.6.0 release built with Go 1.14 and refined DATA-frame validation and reports. ### Related projects - Related projects include H2O, nghttp2, HAProxy, HTTP/2 libraries in language ecosystems, the IETF HTTP working group specifications, RFC 7540, RFC 7541, and HPACK test-case collections. ### Quellen - - - - - - - ## Sicherheitshinweise broad file, network, media, or database tool signal. - **Geiger-Risiko:** blue / mittel - broad file, network, media, or database tool signal ## Details aus der Quelldatenbank - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** h2spec - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Andere Paketmanager-Einträge - Nix - h2spec: normalized package name match | nixpkgs package indexes: pkgs/by-name/h2/h2spec/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Verwandte Links - [Source-control packages](https://www.automicvault.com/de/pkg/source-control-tools/) - Belongs to a source-control command family. - [Secret-risk packages](https://www.automicvault.com/de/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/de/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/de/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [go](https://www.automicvault.com/de/pkg/brew/go/) - Build dependency declared by Homebrew. - [counterfeiter](https://www.automicvault.com/de/pkg/brew/counterfeiter/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [fake-gcs-server](https://www.automicvault.com/de/pkg/brew/fake-gcs-server/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [gor](https://www.automicvault.com/de/pkg/brew/gor/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [gotests](https://www.automicvault.com/de/pkg/brew/gotests/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [gotestsum](https://www.automicvault.com/de/pkg/brew/gotestsum/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [htmltest](https://www.automicvault.com/de/pkg/brew/htmltest/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [mockery](https://www.automicvault.com/de/pkg/brew/mockery/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [richgo](https://www.automicvault.com/de/pkg/brew/richgo/) - Shares av.db curated category or tags: cli, developer-tools, go, testing. - [cassowary](https://www.automicvault.com/de/pkg/brew/cassowary/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, developer, developer-tools, go, http. ## Combined YAML source View the package source record on GitHub. [combined/h2spec.yml](https://github.com/automic-vault/db/blob/main/combined/h2spec.yml) ## Quellen - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph