# h2spec を Homebrew, Nix でインストール

h2spec のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:h2spec
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install h2spec
```

  証拠: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#h2spec
```

  証拠: nixpkgs package indexes: pkgs/by-name/h2/h2spec/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## パッケージ情報

- **パッケージキー:** brew:h2spec
- **パッケージマネージャ:** Homebrew
- **バージョン:** 2.6.0
- **ソース概要:** Conformance testing tool for HTTP/2 implementation
- **ホームページ:** <https://github.com/summerwind/h2spec>
- **リポジトリ:** <https://github.com/summerwind/h2spec>
- **最終更新:** 2026-07-27T14:32:22+02:00
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- h2spec (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 2.6.0
## プロジェクトの歴史と使われ方

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.

### プロジェクトの歴史

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.

### 採用の歴史

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.

### 使われ方

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.

### パッケージ好きにとっての重要性

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.

### タイムライン

- 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.

### ソース

- <https://formulae.brew.sh/formula/h2spec>
- <https://github.com/summerwind/h2spec>
- <https://github.com/summerwind/h2spec/releases>
- <https://httpworkshop.org/workshop2015/presentations/moto-h2spec.pdf>
- <https://raw.githubusercontent.com/summerwind/h2spec/master/README.md>
- <https://www.rfc-editor.org/rfc/rfc7540>
- <https://www.rfc-editor.org/rfc/rfc7541>


## セキュリティノート

broad file, network, media, or database tool signal.

- **Geiger リスク:** blue / 中
- broad file, network, media, or database tool signal

## 他のパッケージマネージャ記録

- 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


## Combined YAML source

View the package source record on GitHub. [combined/h2spec.yml](https://github.com/mxcl/pkgdb/blob/main/combined/h2spec.yml)


## ソース

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
