The first thing I checked was how hashing is implemented and two things stand out to me:
1. Input must be valid UTF-8. 2. stdin is read to EOF instead of being read incrementally
Neither are ideal and can make ut unfit for a fair few use cases.
I find myself reaching for tools like it-tools.tech or other random sites every now and then during development or debugging. So, I built a toolkit with a sane and simple CLI interface for most of those tools.
For the curious and lazy, at the moment, ut has tools for,
- Encoding: base64 (encode, decode), url (encode, decode)
- Hashing: md5, sha1, sha224, sha256, sha384, sha512
- Data Generation: uuid (v1, v3, v4, v5), token, lorem, random
- Text Processing: case (lower, upper, camel, title, constant, header, sentence, snake), pretty-print, diff
- Development Tools: calc, json (builder), regex, datetime
- Web & Network: http (status), serve, qr
- Color & Design: color (convert)
- Reference: unicode
For full disclosure, parts of the toolkit were built with Claude Code (I wanted to use this as an opportunity to play with it more). Feel free to open feature requests and/or contribute.
1. Input must be valid UTF-8. 2. stdin is read to EOF instead of being read incrementally
Neither are ideal and can make ut unfit for a fair few use cases.