A jq clone focussed on correctness, speed, and simplicity

jq in a different dress. As far as I can see the syntax is esentially the same but it is faster and wants to be 'correct'. Neat!

Update multiple repositories in with one command.

Similar to git-xargs but seems to work for repositories not hosted on Github. Takes any kind of script and applies it to all repositories you pass in. Very nice! Only the name is a bit worse.

GReppablejsON!

Super awesome for de-structuring json responses to then simply work with through grep or other text-only speaking stream tools on the command line.

JSON Stream Editor (command line utility).

Another similar-but-different query language based tool to jq - just with what seems like much simpler syntax at least for simple queries.
Not sure how well it fares for more advanced requirements, but it might just do fine.

Very interesting, the name basically gives the game away.
You give the tool a list of git(hub) repositories and a command (or more advanced script files) and it runs it against them.

You could for example create a file in each one. Or change some variable. Or grep and sed something from one thing to another thing. Or or or.

Honestly not seeing myself using it that often - but the fact it exists is fascinating to me, and the naming is just genius. Though I am a little sad that it seems to only work for Github projects.

jq for binary formats - tool, language and decoders for working with binary and text formats

I suppose the description says it all. There are some usage examples on the README.md and they look avery intriguing - basically exploring an mp3 file kinda like through a hexdump/hexviewer but with jq-like query language built in

Same thing as GRON - turn JSON into stream-friendly (i.e. greppable) destructured text.
Just faster! I suppose. Haven't really tried it myself

A JSON Query Language CLI tool. A little like the venerable jq a little not, has different selection (or 'query') syntax.

Basically you pass in JSON to select specific JSON from whatever data.
Feels a little weird to me at first, but might actually be easier for intermediate/advanced use cases then the mind-bending mess jq sometimes turns into for me

(or rather, the constant trial and error with jiq that it turns into)