envchain VS secretlint

I use https://github.com/sorah/envchain. It stores your secrets in Keychain (macOS) or gnome-keyring.

Credentials are often stored as raw text in .config/ or ~/.aws. These can be found in 1Password Shell Plugins, op run, zenv, envchain, etc. to avoid storing raw tokens in files.

You have envchain to store secrets as ENV variables in your keyring and execute commands:

https://github.com/sorah/envchain

Not really something you would use for production web apps, I think envconsul covers that usecase:

https://github.com/hashicorp/envconsul

Azu created 500+ npm packages, wrote and maintains a number of popular command line tools for JavaScript. textlint has 2,751 stars, Secretlint has 698 stars. honkit for building books has 2,896 stars.

In most cases, you can't automatically fix any confidential information you find, but I've noticed that it's OK to automatically remove or mask any confidential information that has been left in .bash_history or .zsh_history. To automatically modify API tokens left in history files, Secretlint v6 adds a --format=mask-result formatter .

Software development: textlint, Secretlint, HonKit and other development and maintenance.

Continuously committed repositories include JSer.info, textlint, and JavaScript Primer, etc. On the other hand, the newly created ones after the launch of GitHub Sponsors include philan.net, HonKit, Secretlint, etc.

secretlint is pluggable linting tool to prevent committing credential like SSH private key, GCP Access token, AWS Access Token, Slack Token, and npm auth token.

secretlint is a pluggable linting tool to prevent committing credential.

You can setup pre-commit Hook per project or pre-commit Hook globally. This git's pre-commit prevent you to commit your credentials like GitHub Token, SSH key, AWS crendentials.