Automic VaultAutomic Vault

brew

使用 Homebrew, Nix 安装 jikken

查看 jikken 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install jikken

local Homebrew formula metadata

Linux

Nix已验证 · 92%
nix profile install nixpkgs#jikken

nixpkgs package indexes · pkgs/by-name/ji/jikken/package.nix · 来源: api.github.com

概览

软件包摘要

Powerful, source control friendly REST API testing toolkit

历史

项目历史与用法

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.

安全态势

风险级别:绿色

narrow executable package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • narrow executable package without higher-risk signals

信号

  • metadata:no-higher-risk-signals

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 6 个平台目标。
  • 构建元数据列出 2 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

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

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
./.jikken

可执行文件

已安装的可执行文件

命令类型暴露范围备注
jkcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-26
管理器版本0.8.4
管理器更新时间
本地数据OK
上游当前
检测到的最新版本v0.8.4

https://github.com/jikkenio/jikken

  • 信息No package-manager update timestamp was available.低 置信度

安装元数据

软件包元数据

软件包键brew:jikken
版本0.8.4
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/jikken
主页https://jikken.io/
仓库https://github.com/jikkenio/jikken
上游文档https://jikken.io/docs
许可证MIT
源码归档https://github.com/jikkenio/jikken/archive/refs/tags/v0.8.4.tar.gz
构建依赖pkgconf, rust
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namejikken
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

Nix95%

jikken

nix profile install nixpkgs#jikken
  • normalized package name match
  • 匹配方式:Jikken
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ji/jikken/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • 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