logs: never pass a raw error object to console.* - #408
Merged
Conversation
* feat: surface named environments in admin Co-Authored-By: QM <qm@users.noreply.github.com> * refactor: clarify environment metadata response --------- Co-authored-by: Sprite <noreply@sprites.dev> Co-authored-by: QM <qm@users.noreply.github.com>
An error object can carry HTTP response bodies, connection strings, or credential material in its properties — in a codebase that handles decrypted credentials, dumping it wholesale into logs is a leak vector. Wrap every raw error passed to console.* in errMessage(...) across src/ (String(e) in plugins that cannot import core utilities) and enforce the pattern with a no-restricted-syntax lint rule so new call sites cannot regress. Local scripts and test CLI crash handlers keep full stacks for debugging.
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.
An error object can carry HTTP response bodies, connection strings, or credential material in its properties — in a codebase that handles decrypted credentials, dumping it wholesale into logs is a leak vector. Wrap every raw error passed to console.* in errMessage(...) across src/ (String(e) in plugins that cannot import core utilities) and enforce the pattern with a no-restricted-syntax lint rule so new call sites cannot regress. Local scripts and test CLI crash handlers keep full stacks for debugging.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.