Skip to content

fix: redact sensitive fields in StructuredLogger#748

Merged
Haroldwonder merged 1 commit into
Haroldwonder:mainfrom
DevKingOche:fix/652-structured-logger-redact-sensitive
Jun 1, 2026
Merged

fix: redact sensitive fields in StructuredLogger#748
Haroldwonder merged 1 commit into
Haroldwonder:mainfrom
DevKingOche:fix/652-structured-logger-redact-sensitive

Conversation

@DevKingOche
Copy link
Copy Markdown

Closes #652

Add a recursive redact() sanitizer to StructuredLogger.formatMessage. Fields named secret_key, private_key, password, kyc_fields, token, authorization, secret, or api_key are replaced with '[REDACTED]' before the log entry is serialised.

Add a recursive sanitizer that replaces values of sensitive keys
(secret_key, private_key, password, kyc_fields, token, authorization,
secret, api_key) with '[REDACTED]' before logging.

Closes Haroldwonder#652
@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 1, 2026

@DevKingOche is attempting to deploy a commit to the Harold's projects Team on Vercel.

A member of the Team first needs to authorize it.

@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented Jun 1, 2026

@DevKingOche Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@Haroldwonder Haroldwonder merged commit 5d72827 into Haroldwonder:main Jun 1, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

correlation-id.ts StructuredLogger does not redact sensitive fields

2 participants