Repository navigation
fix: redact credentials in database connection URLs - #8
Open
varshith84 wants to merge 1 commit into
Open
varshith84 wants to merge 1 commit into
varshith84 wants to merge 1 commit into
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.
Closes #6.
Redact the username/password portion of PostgreSQL, Redis, and MySQL URLs in both mask and hash modes, retaining their scheme, host, port, and database path. Passwordless URLs remain intact, including user@host forms that would otherwise match the email rule. Update both README languages and regenerate the tracked bundle.
Validation:
npm run doctor: all checks passednpm test: 219 passednpm run typecheck,npm run bundle, andgit diff --check: passedThis is pattern-based best-effort redaction, consistent with the existing API. Prepared with Codex assistance.