Add sealed-env to Configuration#1242
Open
davidalmeidac wants to merge 1 commit intoakullpp:masterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds sealed-env to the Configuration section.
Cross-stack library (Java + Node.js) for encrypted .env files at rest, with optional TOTP-bound unsealing for production deploys. Designed against real 2024-2025 supply-chain attacks (Shai-Hulud, tj-actions/changed-files, GhostAction). Spring Boot Starter included.
Per CONTRIBUTING.md: unique selling point is the cross-stack wire format compatible across Node and Java/Spring Boot, public threat model, and TOTP-bound deploys. Not a commercial project. MIT licensed, published on Maven Central (io.github.davidalmeidac) and npm (sealed-env). Description ends with a dot. Entry placed alphabetically (after owner).
Happy to adjust placement or wording on review.