# jwt-cli [![Dependabot Status](https://api.dependabot.com/badges/status?host=github&repo=mike-engel/jwt-cli)](https://dependabot.com) A super fast CLI tool to decode and encode JWTs built in [Rust](https://rust-lang.org). ![Continuous Integration](https://github.com/mike-engel/jwt-cli/workflows/Continuous%20Integration/badge.svg) [![GitHub release](https://img.shields.io/github/tag/mike-engel/jwt-cli.svg)]() `jwt-cli` is a command line tool to help you work with JSON Web Tokens (JWTs). Like most JWT command line tools out there, you can decode almost any JWT header and claims body. Unlike any that I've found, however, `jwt-cli` allows you to encode a new JWT with nearly any piece of data you can think of. Custom header values (some), custom claim bodies (as long as it's JSON, it's game), and using any secret you need. On top of all that, it's written in Rust so it's fast and portable (windows, macOS, and linux supported right now). # Installation Install `jwt-cli` via [Homebrew](https://brew.sh) (macOS), [Cargo](https://www.rust-lang.org/tools/install) (cross-platform), and [FreshPorts](https://www.freshports.org/www/jwt-cli) (FreeBSD). If you intend to use one of these methods, [skip ahead](#homebrew). You may also install the binary from the [release](https://github.com/mike-engel/jwt-cli/releases) page, if you're unable to use Homebrew or Cargo install methods below. Only 64bit linux, macOS, and Windows targets are pre-built. Sorry if you're not on one of those! You'll need to build it from the source. See the [contributing](#contributing) section on how to install and build the project. You should install it somewhere in your `$PATH`. For Linux and macOS, a good place is generally `/usr/local/bin`. For Windows, there isn't a good place by default :(. ## Homebrew ```sh # Install jwt-cli brew install mike-engel/jwt-cli/jwt-cli # Ensure it worked ok by running the help command jwt help ``` ## Cargo If your system [supports](https://forge.rust-lang.org/platform-support.html) it, you can install via Cargo. Make sure you have Rust and Cargo installed, following [these instructions](https://www.rust-lang.org/tools/install) before proceeding. ```sh cargo install jwt-cli ``` The binary installs to your Cargo bin path (`~/.cargo/bin`). Make sure your `$PATH` environment variable includes this path. ## FreshPorts If you're on FreeBSD, you can use the `pkg` tool to install `jwt-cli` on your system. ```sh pkg install jwt-cli ``` Big thanks to Sergey Osokin, the FreeBSD contributor who added `jwt-cli` to the FreeBSD ports tree! ## GoFish `jwt-cli` is also available on Windows, macOS, and Linux using GoFish. See [gofi.sh](https://gofi.sh/index.html#install) for instructions for getting GoFish. After installing GoFish, run `jwt-cli` with: ```sh gofish install jwt-cli ``` ## Arch Linux `jwt-cli` is available in the Arch Linux [community repository](https://archlinux.org/packages/community/x86_64/jwt-cli/) and can be installed via [pacman](https://wiki.archlinux.org/title/Pacman): ```sh pacman -S jwt-cli ``` # Usage For usage info, use the `help` command. ```sh # top level help jwt help # command specific help jwt help encode ``` ## Usage as a pipe The `-` argument tells `jwt-cli` to read from standard input: ```sh jwt encode --secret=fake '{"hello":"world"}' | jwt decode - ``` It's useful when you're dealing with a chain of shell commands that produce a JWT. Pipe the result through `jwt decode -` to decode it. ```sh curl | jq -r .access_token | jwt decode - ``` # Contributing I welcome all issues and pull requests! This is my first project in rust, so this project almost certainly could be better written. All I ask is that you follow the [code of conduct](code_of_conduct.md) and use [rustfmt](https://github.com/rust-lang-nursery/rustfmt) to have a consistent project code style. To get started you'll need `rustc` and `cargo` on your system. If they aren't already installed, I recommend [rustup](https://rustup.rs) to get both! ## Building and running the project Once you have both installed, I recommend running the tests to make sure all is well from the start. ```sh # run the tests cargo test ``` If it built without any errors, you should be able to run the command via `cargo`. ```sh cargo run -- help ``` Or, if you prefer a release build: ```sh cargo run --release -- help ``` # [Code of conduct](code_of_conduct.md) # [Changelog](CHANGELOG.md) # [License](LICENSE.md) ## Contributors ✨ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):

_{Mike Engel} 💻 💬 📖 🤔 🚧 👀 ⚠️ 🐛	_{Kyle Burton} 💻	_{Aaron Schaef} 💻	_hughsimpson 💻 ⚠️	_{Mat Kelly} 💻 🐛	_Jason 🐛	_{Ben Berry} 🐛
_{Kevin Lanni} 📖	_{Kosta Krauth} 💻 ⚠️ 📖	_codedust 💻 🤔 ⚠️	_{Liz Frost} 💻	_{Carl Harris} 💻 ⚠️	_{Yusuke Kominami} 💻 📖

This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!