installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%

brew install jikken

local Homebrew formula metadata

Linux

Nixvérifié · 92%

nix profile install nixpkgs#jikken

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

aperçu

Résumé du paquet

Powerful, source control friendly REST API testing toolkit

Liens du projet

Commandes et alias

jk

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

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

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

narrow executable package without higher-risk signals

Signaux

metadata:no-higher-risk-signals

Comportement d'installation

Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
Les métadonnées de compilation listent 2 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

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

exécutables

Exécutables installés

Commande	Type	Exposition	Note
`jk`	cli	exécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-26

version du gestionnaire0.8.4

gestionnaire mis à jour

données localesOK

amontà jour

dernière version détectéev0.8.4

https://github.com/jikkenio/jikken

infoNo package-manager update timestamp was available.confiance faible

métadonnées d'installation

Métadonnées du paquet

Clé du paquet	brew:jikken
Version	0.8.4
Gestionnaire de paquets	Homebrew
Page du gestionnaire de paquets	https://formulae.brew.sh/formula/jikken
Page d'accueil	https://jikken.io/
Dépôt	https://github.com/jikkenio/jikken
Docs amont	https://jikken.io/docs
Licence	MIT
Archive source	https://github.com/jikkenio/jikken/archive/refs/tags/v0.8.4.tar.gz
Dépendances de compilation	pkgconf, rust
Bouteille	disponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrew	non défini
Service	aucun déclaré

faits du registre

Détails de la base source

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

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

jikken

nix profile install nixpkgs#jikken

normalized package name match
Correspondance par : 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

graphe de paquets

Les liens viennent du graphe local de relations entre paquets, des suppléments, des dépendances, des correspondances d'écosystèmes et de l'appartenance aux hubs.

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/jikken.yml

Sources utilisées

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

Installer jikken avec Homebrew, Nix