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

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

## インストール

```sh
sudo av install brew:jikken
```

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

### macOS

- Homebrew (100%):

```sh
brew install jikken
```

  証拠: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#jikken
```

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

## パッケージ情報

- **パッケージキー:** brew:jikken
- **パッケージマネージャ:** Homebrew
- **パッケージマネージャページ:** <https://formulae.brew.sh/formula/jikken>
- **バージョン:** 0.8.4
- **ソース概要:** Powerful, source control friendly REST API testing toolkit
- **ホームページ:** <https://jikken.io/>
- **リポジトリ:** <https://github.com/jikkenio/jikken>
- **上流ドキュメント:** <https://jikken.io/>
- **ライセンス:** MIT
- **ソースアーカイブ:** <https://github.com/jikkenio/jikken/archive/refs/tags/v0.8.4.tar.gz>
- **生成日時:** 2026-08-04T22:13:35+00:00

## 実行可能ファイル

- jk (cli)
- jk (エイリアス)

## ビルド依存関係

- pkgconf
- rust

## インストール挙動

- post-install フック: 未定義
- Bottle: 利用可能 対象 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux

## バージョンと鮮度

- ページ生成日: 2026-08-04
- マネージャ版: 0.8.4
- ローカルデータ: OK
- 上流リポジトリ: https://github.com/jikkenio/jikken
- 検出された最新: v0.8.4 (最新)
- 情報: No package-manager update timestamp was available.
## プロジェクトの歴史と使われ方

Jikken is a Rust-based command-line tool for source-control-friendly REST API testing. It uses JKT test definition files, expressed in YAML or JSON, so API checks can live beside application code and run through the `jk` command in local shells or CI jobs.

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

The project describes its origin as a tool built to validate complex data APIs used by analytics dashboards while fitting into source control and CI/CD workflows. Its first public release, v0.1.0, shipped at the end of 2022 with basic YAML/JSON test definitions, request execution, response comparisons, tags, variables, extraction, dependencies, and iteration support.

Through 2023 and 2024, Jikken evolved from a simple runner into a broader API-testing toolkit. The changelog shows the move to command-oriented usage with `jk run` and `jk dryrun`, support for staged tests and setup/cleanup, a user-path configuration file, JUnit output, OpenAPI-based test generation, a VSCode extension, secrets, body schemas, generated test data, and formatting and validation commands.

### 採用の歴史

Jikken's distribution history is tied to Rust and cross-platform package channels. The project publishes to crates.io and documents installation through Cargo, Homebrew/Linuxbrew, Chocolatey, prebuilt GitHub release binaries, and source builds, which made it practical for mixed macOS, Linux, and Windows teams to add the same API-test runner to developer machines and CI agents.

### 使われ方

Jikken is used by writing `.jkt` files that define requests and validations, then running `jk run`, `jk dryrun`, `jk list`, `jk format`, or `jk validate`. The documented examples emphasize status-code checks, multi-stage flows, token extraction from one response into later requests, body comparison between API versions, ignored response fields, tag filtering, and recursive discovery.

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

For package collectors, Jikken is a small example of the post-Postman CLI testing niche: API tests stored as plain files, versioned with application code, runnable without a GUI, and packaged through Rust's cargo ecosystem as well as desktop package managers. Its history also shows a common modern path for CLI tools: start with a narrow runner, then add OpenAPI generation, JUnit output, editor support, secrets, and platform binaries as automation use grows.

### タイムライン

- 2022: v0.1.0 introduced the Jikken CLI, YAML/JSON test definitions, variables, comparisons, tags, and ordered test dependencies.
- 2023: v0.4.0 moved execution into explicit commands such as `jk run` and `jk dryrun`; v0.5.0 added optional telemetry and user-path configuration.
- 2024: v0.7.0 added JUnit output, OpenAPI test generation, `jk list`, and a VSCode extension for JKT files.
- 2024: v0.8.0 added secrets, body schemas, generated data for fuzz-style validation, `jk format`, and `jk validate`.
- 2026: v0.8.4 added numeric array indexing for variable extraction from root-level JSON arrays.

### Related projects

- Jikken sits near GUI API clients and test tools such as Postman, Insomnia, Newman, HTTPie, and curl, but its package-manager identity is closer to Rust CLI tools that expect plain files, CI execution, and reproducible installation. Its OpenAPI generation connects it to schema-first API workflows.

### ソース

- <https://api.github.com/repos/jikkenio/jikken/releases?per_page=100>
- <https://crates.io/api/v1/crates/jikken>
- <https://crates.io/crates/jikken>
- <https://github.com/jikkenio/jikken>
- <https://jikken.io/docs/>
- <https://raw.githubusercontent.com/jikkenio/jikken/main/CHANGELOG.md>


## セキュリティノート

narrow executable package without higher-risk signals.

- **Geiger リスク:** グリーン / 低
- narrow executable package without higher-risk signals


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

- Unix: ./.jikken

## Credential files

- Unix: ./.jikken
## ソースデータベース詳細

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** jikken
- **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

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

- Nix - jikken: normalized package name match | nixpkgs package indexes: pkgs/by-name/ji/jikken/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## 関連リンク

- [Source-control packages](https://pkg.so/ja/source-control-tools/) - Belongs to a source-control command family.
- [Terminal utility packages](https://pkg.so/ja/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Text processing packages](https://pkg.so/ja/text-processing-tools/) - Matched text, document, or structured-data processing metadata.
- [Developer build packages](https://pkg.so/ja/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata.
- [pkgconf](https://pkg.so/ja/brew/pkgconf/) - Build dependency declared by Homebrew.
- [rust](https://pkg.so/ja/brew/rust/) - Build dependency declared by Homebrew.
- [ansible-lint](https://pkg.so/ja/brew/ansible-lint/) - Shares pkgdb curated category or tags: ci, cli, developer-tools, yaml.
- [yamlfmt](https://pkg.so/ja/brew/yamlfmt/) - Shares pkgdb curated category or tags: ci, cli, developer-tools, yaml.
- [newman](https://pkg.so/ja/brew/newman/) - Shares pkgdb curated category or tags: api-testing, ci, cli, developer-tools.
- [slumber](https://pkg.so/ja/brew/slumber/) - Shares pkgdb curated category or tags: api-testing, cli, developer-tools, yaml.
- [actions-up](https://pkg.so/ja/brew/actions-up/) - Shares pkgdb curated category or tags: ci, cli, developer-tools, yaml.
- [stepci](https://pkg.so/ja/brew/stepci/) - Shares pkgdb curated category or tags: api-testing, ci, cli, developer-tools.
- [gitlab-ci-linter](https://pkg.so/ja/brew/gitlab-ci-linter/) - Shares pkgdb curated category or tags: ci, cli, developer-tools, yaml.
- [yq](https://pkg.so/ja/brew/yq/) - Shares pkgdb curated category or tags: cli, developer-tools, yaml.
- [keploy](https://pkg.so/ja/brew/keploy/) - Local package facts share a topical domain. Shared terms: api, api-testing, cli, developer, developer-tools.
- [resterm](https://pkg.so/ja/brew/resterm/) - Local package facts share a topical domain. Shared terms: api, api-testing, cli, developer, developer-tools.

## Combined YAML source

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


## ソース

- pkg.so package database
- Geiger risk classifier
- package-page enrichment
- curated configuration and credential file locations
- curated package history
- package version freshness
- pkgdb category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph
