Tcrypt Alternatives

Similar projects and alternatives to tcrypt based on common topics and language

cli-guidelines

47 2,782 3.6 CSS tcrypt VS cli-guidelines

A guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.
docopt

29 7,891 0.0 Python tcrypt VS docopt

This project is no longer maintained. Please see https://github.com/jazzband/docopt-ng
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
docopt-ng

5 156 4.8 Python tcrypt VS docopt-ng

Humane command line arguments parser. Now with maintenance, typehints, and complete test coverage.
sss-cli

2 64 10.0 Rust tcrypt VS sss-cli

Command line program for secret-sharing strings
ether

1 0 0.0 Rust tcrypt VS ether

Symmetric key encryption command-line utility. (by solidiquis)
ripgrep

348 44,901 9.3 Rust tcrypt VS ripgrep

ripgrep recursively searches directories for a regex pattern while respecting your gitignore
zoxide

100 18,590 8.2 Rust tcrypt VS zoxide

A smarter cd command. Supports all major shells.
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better tcrypt alternative or higher similarity.

Suggest an alternative to tcrypt

tcrypt reviews and mentions

Posts with mentions or reviews of tcrypt. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-23.

Looking for UX feedback for my encryption/decryption command line utility.
4 projects | /r/commandline | 23 Jul 2022

I made an encryption/decryption tool for learning purposes and was wondering if you guys had feedback on how I could improve this from a user-experience standpoint: Things like CLI argument structure, argument convention, help text, and things of that nature. I'm a noob when it comes to making command-line utilities and am itching to learn about best practices and how best to make my tools feel ergonomic. Any input is appreciated! Thank you.