I found myself asking these questions when working on projects in git more often than I liked so I built SecretZero to help address them: 1. Where are all the secrets in my project? 2. How do I generate new secrets, api keys, or certificates to deploy a whole new environment or application deployment? 3. When were my critical project secrets last rotated? 4. If I needed to bootstrap this entire project from scratch would I be able to do so without manually handling any secrets? 5. How do I document my project's secrets surface area and requirements? SecretZero employs YAML manifests and produces lockfiles (similar to those seen in terraform, node, or python package managers) that get commited with your source code. It includes a builtin web server, expansive cli, MCP server, skills, and can be used for contextless secret handling. Used in conjunction with a local agent it can facilitate seeding of personal secrets so that your agent never needs to prompt you for an API key ever again.

SecretZero

Secrets as code for end to end secrets lifecycle management

Secrets as code for end to end secrets lifecycle management