OpenSSL wrapper to run any command that OpenSSL admits.
the complete solution for node.js command-line programs
JWA implementation (supports all JWS algorithms)
Infer strong typings for commander options and action handlers
Fisk, a distributed compile system
Fisk, a nice distributed compile system
NodeJS OpenSSL wrapper
A module for making CLI applications with NestJS. Decorators for running commands and separating out config parsers included. This package works on top of commander.
Get the version of a binary in semver format
Export commander command as a Fig spec
A testing utility for nest-commander. It builds on top of ideas from @nestjs/testing and is not tied to any test framework directly.
🛹 Modern TypeScript tools for SVG
Commander.js with integrated interactive prompts
A small collection of option validators for commander
A Javascript library to perform OpenSSL RSA Encryption, Decryption, and Key Generation.
MCP server for terminal operations and file editing
Node.js bindings for librdkafka
is a package which gives you a possibility to run every [OpenSSL](https://www.openssl.org/) command in [Node.js](https://nodejs.org/en/) in a handy way. Moreover, parameters like -in, -keyin, -config and etc can be replaced by a raw data ([Buffor](https:/
the complete solution for node.js command-line programs
Prebuilt openssl libraries for platforms VS Code is published on
A wrapper for Commander that automatically sets the version based on your package.json
Redis web-based management tool written in node.js
Self-signed certificate for development use, generated using openssl. Expires in the year 4754 (4754-06-06).
aes, for browserify
It uses OpenSSL `s_client` command to securely connect with server that requires usage of GOST algorithms and client certificates.
Cross-platform way of finding executables in all the paths in $PATH. This is similar to the Unix 'which' command, however, instead of finding the first occurence of the executable in $PATH, it finds all occurences in $PATH. This could be useful if you installed something that modified your PATH and now you're executing a different version but can't figure out what happened. Example: On OS X, OpenSSL is installed in /usr/bin/openssl % which openssl ==> /usr/bin/openssl After installing PostgreSQL: % which openssl ==> /Applications/Postgres.app/Contents/MacOS/bin/openssl If you're trying to diagnose what happened, you can use: % whiches openssl ==> [ [0] "/Applications/Postgres.app/Contents/MacOS/bin/openssl", [1] "/usr/bin/openssl" ] This will show you that the first one that is found in the PATH is the one from Postgres, so if you want to get back your original one, you have to modify your PATH accordingly.