omerta
A security tool that detects secret leaks in Git repositories by matching against actual environment variable values rather than patterns. It is available both as a pre-commit hook and as a CLI.
Timeline (last 90 days)
omerta is a tool made by Sergii Shcherbak, launched on Product Hunt, whose core logic is to detect secrets using the real values in environment files rather than pattern matching.
omerta offers two usage modes: a pre-commit hook (which automatically checks staged files before committing and blocks commits containing real values of environment variables) and a CLI tool (run manually, scanning tracked files or the entire Git history).
omerta needs to read the .env file as a reference to know which values are sensitive.
omerta cannot detect leaked secrets that never appeared in a local .env file (for example, secrets hardcoded from other sources).
omerta is particularly suited to scenarios where a team uses custom environment variable naming, there is no unified secret format, or sensitive values may have already been mixed into the project history and a comprehensive check is needed.
As a complementary tool, omerta does not change the fact that protecting the .env file itself from being committed remains the first line of defense, and no tool can replace good security habits such as regularly rotating secrets.
All Facts (6)
omerta is a tool made by Sergii Shcherbak, launched on Product Hunt, whose core logic is to detect secrets using the real values in environment files rather than pattern matching.
50%Unverifiedomerta offers two usage modes: a pre-commit hook (which automatically checks staged files before committing and blocks commits containing real values of environment variables) and a CLI tool (run manually, scanning tracked files or the entire Git history).
50%Unverifiedomerta needs to read the .env file as a reference to know which values are sensitive.
50%Unverifiedomerta cannot detect leaked secrets that never appeared in a local .env file (for example, secrets hardcoded from other sources).
50%Unverifiedomerta is particularly suited to scenarios where a team uses custom environment variable naming, there is no unified secret format, or sensitive values may have already been mixed into the project history and a comprehensive check is needed.
50%UnverifiedAs a complementary tool, omerta does not change the fact that protecting the .env file itself from being committed remains the first line of defense, and no tool can replace good security habits such as regularly rotating secrets.
50%