# Install jikken with Homebrew, Nix Powerful, source control friendly REST API testing toolkit. Version 0.8.4 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:jikken ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install jikken ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#jikken ``` Evidence: nixpkgs package indexes: pkgs/by-name/ji/jikken/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:jikken - **Package manager:** Homebrew - **Package manager page:** - **Version:** 0.8.4 - **Source summary:** Powerful, source control friendly REST API testing toolkit - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MIT - **Source archive:** - **Generated:** 2026-07-08T18:08:21+00:00 ## Executables - jk (cli) - jk (alias) ## Build dependencies - pkgconf - rust ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 0.8.4 - Local data: ok - Upstream repository: https://github.com/jikkenio/jikken - Upstream latest detected: v0.8.4 (current) - info: No package-manager update timestamp was available. ## Project history and usage 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. ### Project history 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. ### Adoption history 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. ### How it is used 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. ### Why package nerds care 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. ### Timeline - 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. ### Sources - - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - 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 Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** jikken - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - 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 ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [pkgconf](https://www.automicvault.com/pkg/brew/pkgconf/) - Build dependency declared by Homebrew. - [rust](https://www.automicvault.com/pkg/brew/rust/) - Build dependency declared by Homebrew. - [newman](https://www.automicvault.com/pkg/brew/newman/) - Shares av.db curated category or tags: api-testing, ci, cli, developer-tools. - [hurl](https://www.automicvault.com/pkg/brew/hurl/) - Shares av.db curated category or tags: api-testing, cli, developer-tools. - [keploy](https://www.automicvault.com/pkg/brew/keploy/) - Shares av.db curated category or tags: api-testing, cli, developer-tools. - [req](https://www.automicvault.com/pkg/brew/req/) - Shares av.db curated category or tags: api-testing, cli, developer-tools. - [resterm](https://www.automicvault.com/pkg/brew/resterm/) - Shares av.db curated category or tags: api-testing, cli, developer-tools, rest. - [gitlab-ci-linter](https://www.automicvault.com/pkg/brew/gitlab-ci-linter/) - Shares av.db curated category or tags: ci, cli, developer-tools, yaml. - [slumber](https://www.automicvault.com/pkg/brew/slumber/) - Shares av.db curated category or tags: api-testing, cli, developer-tools, yaml. - [stepci](https://www.automicvault.com/pkg/brew/stepci/) - Shares av.db curated category or tags: api-testing, ci, cli, developer-tools. ## Combined YAML source View the package source record on GitHub. [combined/jikken.yml](https://github.com/automic-vault/db/blob/main/combined/jikken.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - 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