I too have been using sops for years, and agree -- dotenvx encryption seems very similar to sops.
I'd prefer an integration between dotevnx and sops where dotevnx handles the UX of public env and injection, while leveraging sops for secret management and retrieval. Additionally, being able to have multiple keys for different actors is important.
Having a single `.env.keys` file feels risky and error prone. dotenvx encourages adding your various env files, such as `.env.production`, to vcs, and you're one simple mistake away from committing your keyfile and having a bad day.
If sops is not to be integrated, dotenvx could take some inspiration where the main key is encrypted in the secrets file itself, and you can define multiple age key recipients, each of which can then decrypt the main key.
> Brig. Gen. Pat Ryder, Pentagon press secretary, told reporters Friday that an F-22 fighter aircraft based at Joint Base Elmendorf-Richardson shot down the object using the same type of missile used to take down the balloon nearly a week ago.[0]
Shameless plug - I've been building the startup Wedge[0]. In addition to helping prevent application fraud, I deeply believe applicants are _people_ and have more to share beyond a resume.
We enable companies to asynchronously collect a short series of video responses from an applicant either at application time or later in the process.