Thanks for this great tool!

Hoping to get some clarification here surrounding commits. I've setup automation around Gitleaks to scan commits as they happen on a few repositories, however, the tool is alerting when the secret is first committed, and then alerting a second time when it's removed (not a file deletion, but a line removal).

Is there any configuration options to disable alerts w

It’s probably straight-forward for some people using Docker more regularly than me, but it took a while to find out how to run truffleHog from Docker with my locally cloned repo:

cd /path/to/git_repo
docker run --rm -v `pwd`:/proj dxa4481/trufflehog file:///proj

• -v mounts the current working dir (`pwd`) to the /proj dir in the Docker container
• file:///proj refer

Expected behavior

When writing the email in a wrong format error message appears. When rotating the screen the message should be preserved.

Actual behavior

When rotating the screen the message is not preserved.

Steps to reproduce the behavior

1. Press Log In
2. Enter Email address and press Next. An error message will be shown
3. Rotate the screen. The message is not sho

Is your feature request related to a problem? Please describe.
Investigate github.com/google/go-containerregistry to replace the heroku/docker-registry-client which seems to be unmaintained.

Describe the solution you'd like
Check the go-containerregistry library and see if it fits our needs.

Describe alternatives you've considered
We already use a forked version of the docker-

We want to enforce talisman for specific repositories, potentially as a part of setup/build scripts. Currently the install.sh script is hardcoded as a pre-push hook.

We would like to be able to easily install talisman (e.g. via an install script) for specific repositories but as a pre-commit hook. Ideally, the install.sh script should be able to take a parameter just like the global insta

Project References help us to build specic package.

Currently, we need to build before developing a specifc package.

cd <project-root>
yarn run build

Include the following:

• history of fugacious
• why fugacious has its own org
• how 18F manages control over fugacious.18f.gov
• link to SSP/ATO controls documentation